Manage team roles and product access
AtomicPay team access lets a business owner invite collaborators without giving every user full control of products, finance, sales, and settings.
Use this guide when you are inviting a teammate, changing a collaborator's role, limiting access to selected products, or removing access from someone who should no longer manage the business.
What team access controls
| Area | Purpose |
|---|---|
| Role | Defines the collaborator's main responsibility in the business. |
| Permissions | Controls specific actions such as viewing balance or creating withdrawals. |
| Product access | Limits whether a collaborator can access all products or only selected products. |
| Invite status | Shows whether the user accepted, is still invited, or needs the invite resent or revoked. |
| Business access | Connects the collaborator to one business workspace, not every business in the account. |
Common roles
| Role | Best for |
|---|---|
| Owner | The primary business owner with full responsibility for the workspace. |
| Admin | A trusted manager who helps control business settings, products, and team operations. |
| Project manager | A user who manages products, launch setup, and operational workflows. |
| Support manager | A user who supervises support workflows and support team access. |
| Support agent | A user who needs limited access for customer support, links, upgrades, sales, or subscriptions. |
| Finance user | A user who needs finance visibility or withdrawal-related permissions without full admin access. |
| Employee | A general collaborator with restricted access based on assigned permissions. |
Product access modes
Product access decides whether a collaborator can work across the whole catalog or only selected products.
| Access mode | Use it when |
|---|---|
| All products | The collaborator is trusted to work across the full business catalog. |
| Selected products | The collaborator should only support, manage, or report on specific products. |
Use selected product access for support agents, contractors, launch assistants, or team members who should not see every product in the business.
Invite a collaborator
- Confirm you are in the correct business workspace.
- Open the company or account team area.
- Start a new employee or collaborator invite.
- Enter the collaborator's email.
- Choose the role that matches their responsibility.
- Choose all-product access or selected-product access.
- Select the products the user should access when using restricted access.
- Add specific permissions when the role requires them.
- Send the invite.
- Confirm the invite is accepted before relying on that user for launch operations.
Finance permissions
Finance access should be granted deliberately because it can expose balance and withdrawal information.
| Permission | Use it when |
|---|---|
| View balance | The user needs to monitor available, pending, and total funds. |
| List withdrawals | The user needs to review withdrawal history. |
| View withdrawal details | The user needs to inspect a specific payout request. |
| Create withdrawals | The user is trusted to request payouts from available balance. |
For most teams, finance visibility and withdrawal creation should not be bundled automatically with product or support access.
Review and update access
Review collaborator access whenever the team changes, a product launch ends, or a support contractor no longer needs access.
Check:
- Role still matches the collaborator's job.
- Product access is not broader than needed.
- Finance permissions are still appropriate.
- Invited users accepted the invite with the correct account.
- Old or unused invites are resent or revoked.
- Former collaborators are removed promptly.
Best practices
- Give users the least access they need to do the job.
- Use selected-product access for support agents and temporary collaborators.
- Keep finance permissions separate from general admin work unless the user truly needs payout control.
- Review access before launches, after launches, and when an employee leaves.
- Revoke pending invites that were sent to the wrong email or accepted with the wrong account.
FAQ
Should every manager be an admin?
No. Use admin access only for trusted users who need broad control. Project, support, finance, and selected-product access can often cover the work without exposing the full business.
How do I give support access without exposing every product?
Invite the support user with the right support role and choose selected-product access. Then select only the products they should support.
Can a finance user request withdrawals?
Only if they have permission to create withdrawals. A user may be able to view balance or withdrawal history without being allowed to request payouts.
What should I do if someone accepted an invite with the wrong account?
Review the collaborator record, revoke or remove the incorrect access when needed, and send a new invite to the correct email/account.