Permissions Management

RudderStack’s permissions management feature gives you the ability to:

• Restrict edit permissions for business-critical objects to selected users in your organization.
• Limit access to the product features where PII is exposed (for example, Live Events, debug logs, etc.) for compliance purposes.

Set granular access controls

When you invite a member to your organization, RudderStack lets you assign any of the two default organization roles to them - Org Admin or Org Member.

With RudderStack’s granular access control features, admins can lock down business-critical objects to a select list of people. They can also restrict PII(Personally Identifiable Information) access to certain users.

With these features, you can allow certain data pipelines to be edited only by the users with the required access. Also, you can ensure your access controls are in compliance with the major data regulations like SOC2, GDPR, CCPA, HIPAA, etc.

All the access-related changes are recorded in the audit logs.

Set permissions for individual resources

Go to the Permissions tab to set permissions for a particular resource (source, destination, or model) in the workspace. You can also specify members who can make changes to these resources.

Only users with admin permissions can see the Permissions tab.

Permissions scope

The permissions set for a particular resource let you:

• Connect/disconnect a resource with another resource. For example, source to destination, source to tracking plan, transformation to destination, model to reverse ETL source, etc.
• Enable, disable, or delete a resource.
• Edit or change the resource-specific configuration.

Any action involving setting up a connection between two resources or linking/de-linking a resource with another resource requires edit permissions for both the resources. The only exception is the SQL Models which can used without explicitly setting any edit permissions.

Specify members with edit permissions

To specify members who can make changes to a given resource, follow these steps:

1. Go to the resource and click the Permissions tab:

2. Under Who can make changes?, select any of the following two options:

   • Anyone with write access: All the members with the admin permissions can make changes to the resource.
   • Only people you select: With this option, only specific members can make changes to the resource.

3. To allow specific members of your team to edit the resource, click Only people you select, followed by Add member.

4. Finally, select the team members from the drop-down and click Add Members:

Members with view-only permissions cannot be added as they do not have permissions to modify a resource, by default.

Limit access to PII

RudderStack’s data privacy options let you safeguard your customers’ privacy by controlling who has access to the raw event data containing PII(Personally Identifiable Information). You can allow anyone on your team to access the PII or restrict access only to a select list of members.

Only members with PII permissions can view the customers’ PII in the Live Events and errors logs in your destination’s Events tab:

To set the PII permissions, follow these steps:

1. In your RudderStack dashboard, go to Settings > Workspace > Data Management and scroll down to the Data Privacy section.

2. Under Who can view restricted data?, select the appropriate option:

   • Anyone on your team: All the members in your workspace can view the raw event data containing PII.
   • Only people you select: Only specific members with access can view the raw data.

3. To allow specific members of your team to edit the object, click Only people you select, followed by Add member.

4. Finally, select the workspace members from the drop-down and click Add Members:

If the admins are removed from the access list, RudderStack will restrict them from viewing the PII.

Questions? Contact us by email or on Slack