Overview
Rapyd Cloud gives you control over who can access your account and what they can do within it. Each team member is assigned a role, and each role comes with a defined set of permissions covering areas like billing, site management, and user administration. Choosing the right role for each person keeps your account secure and avoids unintended changes.
There are four roles available: Administrator, Billing Manager, Member, and Guest. Roles can be customized further for Billing Managers, Members, and Guests by granting or restricting specific permissions beyond the defaults.
In this article, you will find a breakdown of each role, a full permissions reference table, and instructions for editing a team member's role.
Roles
Administrator
Administrators have full access to the dashboard, including all sites, billing, and user management. This is the highest level of access available to a team member.
Environment access: All environments
Can manage billing: Yes
Can manage team members: Yes
Can set up new environments: Yes
Can manage domains: Yes
Can contact support: Yes
Can delete sites: Yes
Important:
Only the account owner can delete the account. Administrators can manage all other aspects of the account, including assigning and editing roles for other team members and deleting environments and sites.
Billing Manager
Billing Managers can handle financial administration for the account. Outside of billing, their access is limited to sites explicitly assigned to them.
Environment access: Assigned environments only (can be expanded to all)
Can manage billing: Yes
Can manage team members: No
Can set up new environments: No (permission required)
Can manage domains: No (permission required)
Can contact support: No (permission required)
Can delete sites: No
Note:
Billing Managers can manage all subscriptions within the account, including downloading invoices and updating payment methods. They can only manage sites within the environments assigned to them.
Member
Members are focused on site work. They can access and manage the sites assigned to them, but have no visibility into billing or account-wide settings.
Environment access: Assigned environments only (can be expanded to all)
Can manage billing: No
Can manage team members: No
Can set up new environments: No (permission required)
Can manage domains: No (permission required)
Can contact support: No (permission required)
Can delete sites: No
Guest
Guests have the most restricted access of any role. They are limited to the sites assigned to them and cannot see team member or billing information.
Environment access: Assigned environments only
Can manage billing: No
Can manage team members: No
Can set up new environments: No
Can manage domains: No
Can contact support: No
Can delete sites: No
Tip:
The Guest role works well for external collaborators, contractors, or clients who need access to specific sites without visibility into the rest of your account.
Additional permissions
Billing Managers and Members can be granted the following permissions on top of their base role. Each one applies at the account level, not the environment level.
Set up new environments: The team member can deploy new environments under the account's subscription
Manage domains: The team member can manage all domains across the account
Contact support: The team member can open support tickets on behalf of the account
These permissions are off by default and must be enabled individually. They can be set when inviting a team member or updated at any time from the Team page.
Note: Guests cannot be granted additional permissions.
Permissions reference
The table below gives a full comparison of what each role can do by default.
Capability | Administrator | Billing Manager | Member | Guest |
Full dashboard access | ✅ | ❌ | ❌ | ❌ |
Manage team members | ✅ | ❌ | ❌ | ❌ |
View other team members | ✅ | ✅ | ✅ | ❌ |
Manage billing | ✅ | ✅ | ❌ | ❌ |
View and download invoices | ✅ | ✅ | ❌ | ❌ |
Change payment details | ✅ | ✅ | ❌ | ❌ |
Access all environments | ✅ | ❌ | ❌ | ❌ |
Access assigned environments | ✅ | ✅ | ✅ | ✅ |
Delete sites | ✅ | ❌ | ❌ | ❌ |
Set up new environments | ✅ | Permission required | Permission required | ❌ |
Manage domains | ✅ | Permission required | Permission required | ❌ |
Contact support | ✅ | Permission required | Permission required | ❌ |
Note: Any team member with access to an environment can create sites within it, up to that environment's plan limit. Site creation is not a separate permission.
Important information
Only the account owner can delete the account. This cannot be delegated to any other role
Access is granted at the environment level. A team member with access to an environment can manage all sites within it, including creating new sites up to the environment's plan limit. There is no site-level access control
Sites can only be deleted by Administrators
Environment access and role permissions are managed separately. A team member's role defines what they can do; their environment access defines where they can do it
Removing a team member takes effect immediately. Removed members lose access to all environments and account data at the point of removal
Conclusion
Understanding which role is right for each person on your team helps keep your account secure and well-organized. Administrators have broad control, while Billing Managers, Members, and Guests can be scoped precisely to what they need.
For instructions on inviting team members, editing roles, and managing environment access, see How to manage team members. If you have questions about roles or need help configuring permissions, our support team is available 24/7.