Manage Portal Users
Overview
Control who can access your Build a Doc portal and what they can do with role-based permissions.
User Roles
| Permission | Admin | Member | Viewer |
|---|---|---|---|
| View subscription details | ✅ | ✅ | ✅ |
| Change subscription plan | ✅ | ❌ | ❌ |
| Create API keys | ✅ | ✅ | ❌ |
| Revoke API keys | ✅ | ⚠️* | ❌ |
| View usage reports | ✅ | ✅ | ✅ |
| Export reports | ✅ | ✅ | ❌ |
| Invite users | ✅ | ❌ | ❌ |
| Remove users | ✅ | ❌ | ❌ |
| Change user roles | ✅ | ❌ | ❌ |
| View audit logs | ✅ | ⚠️** | ❌ |
| Access documentation | ✅ | ✅ | ✅ |
*Member can revoke only their own API keys **Member has limited audit log access
Inviting Users
- Sign in to the portal as an Admin
- Navigate to Users
- Click Add User
- Enter the user’s email address
- Select the role to assign
- Click Send Invitation
The user will be invited to join.
Changing User Roles
- Go to Users in the portal
- Find the user to modify
- Update the role
- Save changes
Removing Users
- Go to Users in the portal
- Find the user to remove
- Click Deactivate
- Confirm the action
What happens:
- User immediately loses portal access
- API keys created by the user remain active
- Consider revoking their API keys as well
Best Practices
Minimum Privilege
Assign the lowest role that allows users to do their job:
- Developers who only view reports → Viewer
- Developers who manage integrations → Member
- IT administrators → Admin
Regular Review
Periodically review user access:
- Remove inactive users
- Verify roles are still appropriate
- Check for users who have left the organisation
Admin Redundancy
Ensure multiple admins exist to:
- Avoid single point of failure
- Coverage during absences