Partner & Reseller Management
Routes under: part
- part > paccpo > add
- part > paccpo > list > all
- part > pacct > list > all
- part > pacct > quick add
- part > phm > l
- part > ptnrprf > list > all
- part > tu > tra > re > details
- part > tu > tra > re > summary
part > paccpo > add
part > paccpo > add
Route: part/paccpo/add
URL: https://admin.myslbb.com/#/part/paccpo/add
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Name, Description, View Active Sessions, Bulk Renew, Manage KYC, Manage Customer Comments, New Customer Auto Renewal, Edit Customer Account, View Financial Transaction Details, Change Customer Account Status, Cancel Future Plan, Manage Service Parameters, View Manage AddOn, Manage Customer Auto Renewal, View Customer Communication, Modify Communication Address, Cancel Service Plan, Download ECaf, Manage Service Parameter (Mac Bindings), View Account Operation Log, Manage On Demand Bill, View Service Usage Details, Manage Customer Subscriber Preferences, Override QOS Policy, Enable Edit Partner
- Actions detected: Auto, Close, Partner, Partner Access policies, Expand All, Collapse All, Select All, Deselect All, Module - Customer, Actions - Active Sessions, Actions - Ticket, Actions - Bulk Renewal, Actions - Account, Actions - Lead, Actions - Auto Renewal, Actions - Access Requests, Actions - Portal Settings, Module - Inventory, Actions - Device Items, Actions - IP Pool
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
create_new
Captured URL: https://admin.myslbb.com/#/part/paccpo/add
part > paccpo > list > all
part > paccpo > list > all
Route: part/paccpo/list/all
URL: https://admin.myslbb.com/#/part/paccpo/list/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Partner, Partner Access policies, New Policy, Default Partner Access Policy, LCO Access
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/part/paccpo/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/part/paccpo/list/all
part > pacct > list > all
part > pacct > list > all
Route: part/pacct/list/all
URL: https://admin.myslbb.com/#/part/pacct/list/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Partner, Partner Account, Quick Create, New Partner, Clear, CSL/0000001, SHREE SIDHHIVINAYAK NET, CSL/0000002, Glance_Amolnet, CSR/0000001, JLR Networks Pvt Ltd, CSR/0000002, Samarth Cable Services, CSR/0000003, Sumit Cables, CSR/0000004, StarNet - Powai, CSR/0000005
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/part/pacct/list/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/part/pacct/list/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/part/pacct/list/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/part/pacct/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/part/pacct/list/all
part > pacct > quick add
part > pacct > quick add
Route: part/pacct/quick-add
URL: https://admin.myslbb.com/#/part/pacct/quick-add
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Partner Name, Partner Network Name, Description, Partner Type, Partner Profile, Business Entity, Access Profile, TDS(in %), GSTIN, Aadhar Number, PAN Number, Agreement Start Date, Agreement End Date, Email Id, Phone, Additional Phone Number(Optional), AddressLine 1, AddressLine 2, Pincode, Sub District, District, State, Default UserName, Default Password, User Email
- Actions detected: Auto, Close, Partner, Partner Account, Create Partner Account, Cancel
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
create_new
Captured URL: https://admin.myslbb.com/#/part/pacct/quick-add
part > phm > l
part > phm > l
Route: part/phm/l
URL: https://admin.myslbb.com/#/part/phm/l
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Partner, Partner Hierarchy Management
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/part/phm/l
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/part/phm/l
part > ptnrprf > list > all
part > ptnrprf > list > all
Route: part/ptnrprf/list/all
URL: https://admin.myslbb.com/#/part/ptnrprf/list/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Partner, Partner Profile, New Simple Partner Profile, New Advanced Partner Profile, Clear Filters, PRF/0002, 100_InRate, PRF/0014, 100EXCLGST, PRF/0025, 100INCLGST_Default_Distributor, PRF/0005, 60_InRate, PRF/0027, 60INCLGST, PRF/0028, 65INCLGST, PRF/0004
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/part/ptnrprf/list/all
create_new
Captured URL: https://admin.myslbb.com/#/part/ptnrprf/list/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/part/ptnrprf/list/all
part > tu > tra > re > details
part > tu > tra > re > details
Route: part/tu/tra/re/details
URL: https://admin.myslbb.com/#/part/tu/tra/re/details
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Select Date Range, Amount Filter
- Actions detected: Auto, Close, Partner, Topup Wallet, Reversal, Apply Filter, Clear Filters
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
ui_tab_2
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details
common_tab_2
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details
common_tab_3
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/details
part > tu > tra > re > summary
part > tu > tra > re > summary
Route: part/tu/tra/re/summary
URL: https://admin.myslbb.com/#/part/tu/tra/re/summary
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Select Date Range
- Actions detected: Auto, Close, Partner, Topup Wallet, Reversal, Apply Filter, Clear Filters, XLS, CSV
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/summary
ui_tab_1
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/summary
common_tab_1
Captured URL: https://admin.myslbb.com/#/part/tu/tra/re/summary