Teams & Organizations
Keep AWS accounts, resources, billing, and access grouped around the people responsible for them.
The workspace model
An organization is the boundary for your SnoozeDB work. Its AWS accounts, resources, schedules, recommendations, billing, and activity history stay together.
Invite people to the organization instead of sharing credentials. Each person signs in with their own account, so changes remain attributable in the activity log.
Roles and permissions
Choose the least powerful role that still lets someone do their job. You can change an admin or member role later.
| Role | What it is for |
|---|---|
| owner | Controls the organization, including ownership transfer and deletion. There is one owner at a time. |
| admin | Manages collaborators, organization settings, billing, AWS connections, and resources. An admin cannot transfer ownership or delete the organization. |
| member | Works inside the organization and can view its shared dashboard data, without access to admin-only changes or user activity logs. |
Invite collaborators
Open Collaborators from the dashboard, then invite the person by email.
- 01
Enter their email
Use the address they will use to sign in to SnoozeDB.
- 02
Choose a role
Select Admin for workspace management or Member for day-to-day access.
- 03
Send the invite
The recipient joins the organization through the invitation flow.
Manage collaborators
Owners and admins can keep access current from the Collaborators page.
- Promote a member to admin or move an admin back to member.
- Remove someone who no longer needs access.
- Review User logs to see who changed roles, invitations, schedules, or organization settings.
Transfer ownership
Only the current owner can transfer ownership, and the recipient must already belong to the organization. Start the transfer from Organization settings and confirm the intended collaborator.
After a successful transfer, the recipient becomes owner and the previous owner becomes an admin.
Work across organizations
Use separate organizations when AWS accounts, teams, or billing should remain independent. Each organization has its own plan, resource quota, settings, and audit history.
Switch the active organization from the dashboard before making a change. The current organization determines which AWS accounts and resources you are working with.
Troubleshooting
- If an invite goes to the wrong address, remove or replace it instead of sharing the original link.
- If a control is unavailable, check your role and whether the organization requires MFA for management actions.
- If the wrong resources appear, confirm that you selected the intended organization.
- If the owner is unavailable, contact SnoozeDB support; admins cannot take ownership themselves.