This task changes workspace identity, access or public settings and should be reviewed before saving. This guide focuses on how to give each teammate only the access required and remove it when responsibilities change.
Open the correct business team
Team access belongs to a specific business workspace. Confirm the business header before reviewing members or invitations; access to one business should not imply access to another.
Compare roles with real responsibilities
Review each person’s current work and select the narrowest supported role that lets them complete it. Administrator, moderator and read-only access carry different permissions; avoid choosing the broadest role for convenience.
Check invitations and inactive members
Cancel stale invitations and remove people who no longer work with the business. Do not reuse another person’s seat or share one login, because that removes accountability from the audit history.
Protect financial and customer access
Pay particular attention to permissions that expose customer data, refunds, payout settings or wallet operations. Use a second review before expanding these responsibilities.
Record and repeat the review
After saving, sign in with an appropriate test account or review the resolved role rather than assuming the label changed every permission. Schedule another review when responsibilities or team membership change.
Example: Review Team Access and Permissions
Give a support teammate the narrowest supported role and remove the seat when their work ends; Team is a Pro feature.
If Review Team Access and Permissions is not working
If Team opens Billing, confirm Pro status instead of sharing the owner login.
Confirm the result
- The signed-in account and active business are the intended ones.
- The resolved identity, role or setting matches the requested change.
- Security and access changes have a safe recovery or review path.
- No password, OTP, recovery code or identity number appears in an ordinary message.
When to ask Selstack for help
Contact official Selstack support when the saved result, status or resolved identity still conflicts with the intended record after one refresh. Include the business, page, time, safe reference and visible message. Do not include passwords, OTPs, recovery codes, full card details, BVN, NIN or unmasked bank documents.