Access Control User Guide
Manage organizations, teams, users, roles, API keys, RBAC policies, SSO, and audit logs for the Inwire platform.
Who This Guide Is For
- Org administrators
- Platform administrators
- Security teams
Where To Go
| Page |
Use It For |
/access-control/users-roles |
Manage users, invitations, role assignments, and account state. |
/access-control/teams |
Create teams and control team membership. |
/access-control/organizations |
Manage organization settings and top-level ownership. |
/access-control/rbac-policies |
Review and maintain role-based access policies. |
/access-control/api-keys |
Create and rotate API keys for automation. |
/settings/security |
Configure security controls. |
/settings/sso |
Configure SSO where enabled. |
/settings/audit-logs |
Review user and system audit events. |
Core Concepts
| Concept |
Meaning |
| Organization |
The tenant boundary for users, teams, integrations, and most platform resources. |
| Team |
A collaboration boundary inside an organization. |
| Role |
A named permission bundle such as Super Admin, Org Admin, Team Admin, or Member. |
| API key |
A credential for service access and automation. Rotate keys regularly. |
| Audit log |
A durable record of sensitive and operational actions. |
Common Workflows
Onboard a user
- Open Users & Roles.
- Invite the user or activate an existing account.
- Assign the least-privileged role that supports the job.
- Add the user to the correct team.
- Confirm access by checking team-scoped resources.
Create an automation key
- Open API Keys.
- Create a key with a clear owner and purpose.
- Store it in a secret manager.
- Set a rotation date.
- Revoke unused or expired keys.
Best Practices
- Use teams to isolate projects, environments, or business units.
- Avoid shared user accounts; use named users and scoped API keys.
- Review audit logs after role, SSO, and API key changes.
- Keep production deployment permissions limited to approved operators.