Support Central · Account & Access
I Can’t Access the Right Seller Central Account or Function
Use this guide when an approved user cannot sign in, can sign in but sees the wrong access, is missing an expected function, or appears to have the wrong role/account state.
Follow the diagnostic path before opening a ticket. Do not send passwords, OTPs, reset links, session cookies or secret tokens to support.
Account-access diagnosticLogin → context → role → function
01Can you reach Seller Central?If the site itself will not load, that is different from a credential problem.
→
02Can you sign in?Use the normal recovery path once. Never send the password or OTP to support.
03Correct account and role?Successful login does not prove the account context or permission set is correct.
04Still blocked?Open an Account & Access ticket with the missing function and expected role.
Signed in ≠ correct access.Verify account context + role + function
01Start here
Which Access Boundary Is Actually Failing?
Check identity, account context, role and workflow availability separately.
SafeConfirm the URL, use the normal recovery path once, reload after a documented permission update.
StopDo not create duplicate accounts, share credentials or borrow a privileged login.
A. Can you reach the Seller Central login page?No → treat as site/browser/service availability issue. Yes → continue.
↓
B. Can the approved user sign in?No → use the normal recovery path once. Still no → ticket.
↓
C. Correct organisation/account context?No → do not continue workflow work in the wrong account.
↓
D. Expected role/function visible?No → compare approved responsibility with visible access.
↓
E. Still inconsistent?Open one Account & Access ticket with the exact missing function and expected role.
02Problem: I cannot sign in
Use the Approved Recovery Path Once, then Escalate if Access Still Fails
- Confirm Seller Central URL.
- Use the approved account email.
- Use the normal password recovery path once.
- Capture the exact visible error.
- If still blocked, open an Account & Access ticket.
Support needsApproved email, visible error, approximate time, browser/device if relevant.
Never sendPassword, OTP/MFA code, reset link, session cookie or secret token.
Seller Central sign-inScreenshot slot AA-01
Highlight: approved email + recovery control + exact visible error.
Replace with live Seller Central login screenshot.Use fictional/demo credentials only.
03Problem: I can sign in but cannot see the right function
Confirm the Account Context, then Identify the Exact Missing Page or Action
- Confirm account/organisation context.
- Identify the exact missing page/menu/action.
- State the user’s approved responsibility.
- Do not use another person’s privileged account as a workaround.
Seller Central dashboard/account contextScreenshot slot AA-02
Highlight: account identity/context + expected function + user/account control.
Show the real dashboard/account context.Annotate where the expected function should appear.
04Problem: role or permission looks wrong
Compare Approved Responsibility with Visible Capability
Support can investigate a mismatch. It should not bypass the organisation’s approval process for higher privileges.
Missing approved accessOpen a case with expected role + exact missing function.
Unexpected privileged accessDo not use it. Report it so the permission boundary can be corrected.
Role-dependent controlsScreenshot slot AA-03
Use fictional/demo users only; show the minimum role-dependent UI.
Demo operator/supervisor screenshot.Do not expose security-sensitive admin information.
05Problem: onboarding or approval looks stuck
Separate Application Submitted, Approved Account and Function Enabled
- Confirm application state.
- Confirm approval is complete.
- Confirm the account can sign in.
- Confirm required function is enabled for the approved configuration.
- If states disagree, open one Account & Access ticket.
Onboarding / approval stateScreenshot slot AA-04
Show approval/account state only. Never show real KYC or bank data.
Use demo onboarding/account data.No PAN, Aadhaar, GST certificates, bank details or real addresses.
Still blocked?
Build the Ticket around the Access State—not around the Password
Support needs to know who should have access, what they should be able to do and what the system is actually showing.
Good ticket
User: demo.operator@example.com
Account: Demo Studio
Expected role: Warehouse Operator
Missing function: Inbound → Item Intake
Current state: User can sign in but Item Intake is not visible
Evidence: Sanitised dashboard screenshot attached
Bad ticket
“I cannot access anything. My password is ______. Please login and fix it.”
Never include a password, OTP or secret authentication material.