Team Members
Team Members
Section titled “Team Members”Invite team members to your Aureva projects and assign roles. Control who can view, edit, or manage your scripts and keys.
| Role | Description |
|---|---|
| viewer | Read-only access; view projects, scripts, keys, analytics |
| editor | Edit scripts and keys; modify project settings; cannot manage team |
| admin | Full control; add/remove members, change roles, delete project |
Adding Members via Dashboard
Section titled “Adding Members via Dashboard”- Open your project
- Go to Team or Settings → Team
- Click Invite Member
- Enter the member’s email
- Select a role (Viewer, Editor, or Admin)
- Click Send Invite
The member receives access. No separate acceptance flow is required for project members added by the owner.
Permissions Summary
Section titled “Permissions Summary”| Action | Viewer | Editor | Admin |
|---|---|---|---|
| View scripts | ✓ | ✓ | ✓ |
| Upload scripts | ✗ | ✓ | ✓ |
| Edit/delete scripts | ✗ | ✓ | ✓ |
| View keys | ✓ | ✓ | ✓ |
| Create/revoke keys | ✗ | ✓ | ✓ |
| View analytics | ✓ | ✓ | ✓ |
| Edit project settings | ✗ | ✓ | ✓ |
| Invite/remove members | ✗ | ✗ | ✓ |
| Delete project | ✗ | ✗ | ✓ |
User Groups
Section titled “User Groups”Aureva supports user groups for bulk permission management. When a member is in a group, they can inherit the group’s role. Group membership simplifies managing large teams.
Discord Role Mappings
Section titled “Discord Role Mappings”You can auto-grant project access based on Discord roles:
- Map Discord server roles to project access levels (
viewer,editor,admin) - Users with the mapped role automatically get the corresponding project access
- Useful for Discord-integrated workflows
Removing Members
Section titled “Removing Members”- Go to Team in your project
- Find the member to remove
- Click Remove or the three-dot menu → Remove
- Confirm
Only Admins can remove members. You cannot remove yourself if you’re the only Admin—transfer Admin to another member first, or delete the project.
Best Practices
Section titled “Best Practices”- Principle of least privilege — Give users the minimum role they need
- Audit regularly — Review team membership and remove inactive users
- Use Editors for day-to-day — Reserve Admin for project owners
- Document roles — Add a note when inviting (e.g., “Editor for script uploads”)