Members (User management)

RudderStack’s user management feature lets you easily collaborate with other members of your organization. It provides different options to manage users and their permissions in your RudderStack workspace.

Member limit

The following table specifies the number of team members you can add to your workspace in different RudderStack Cloud plans:

Inviting users to your workspace

To invite a member to your RudderStack workspace, follow these steps:

1. Go to Settings > Members and click the Invite member button:

2. Enter the member’s Email and select an appropriate role from the dropdown.

Refer to the Role permissions section below for more information on the Read-Only, Read-Write, and Admin roles.

3. Finally, click Invite. Your teammate will be automatically added to the workspace once they accept the invite.

Role permissions

You can assign any of the following three roles to the member you want to invite to your workspace:

• Read-Only
• Read-Write
• Admin

The following sections list the default permissions associated with each role.

You can also set granular access controls and lock down access to specific RudderStack objects and features to a select list of members in your workspace. For more information, refer to the Permissions Management guide.

Read-Only

This role has the following permissions:

Read-only users can:

• View the connection settings for all destinations. However, they do not have access to view secrets like the access keys.
• View any secrets in the transformation code like the API keys.

Read-Write

A Read-Write user has all permissions of a Read-Only user. In addition, they can modify the following workspace features and options:

Admin

This role has complete access to the RudderStack workspace, including all features in the current RudderStack Cloud plan. It also has some additional permissions related to the workspace settings like managing users, modifying user permissions, enforcing MFA(multi-factor authentication), and more.

Members with this role also have the permissions to set granular access controls for certain business-critical objects and limit PII access to certain users.

The following table details all permissions applicable for the Admin role:

Questions? Contact us by email or on Slack