About resource groups

A resource group represents one or more databases in the Customer 360 page. Users with access to a resource group can build queries and segments against that database and can send data from that database to downstream workflows.

“All resource groups”

Amperity includes one default resource group: “All resource groups”.

Users that are granted access to the “All resource groups” resource group are allowed to interact with all of the databases in the Customer 360 page.

Custom resource groups

Use a custom resource group to support any combination of team member access to brand-specific databases.

Note

Users who are associated with a custom resource group cannot access the Sources page. Access to the Sources page requires users to have access all data available to the tenant.

Users who are associated with a custom resource group may be able to view the Stitch page (depending on their policy), but will not be able to view personally identifiable information (PII).

To add a custom resource group

  1. As a user with Admin privileges, open the Settings page, and then select Security.

  2. Next to Resource Groups, click Add Resource Group.

  3. Enter the name of the custom resource group and a description.

  4. Click Save.

Assign users to resource groups

Assign a user to a policy, and then associate that policy to a resource group. A user may be assigned to more than one policy. A policy may be associated with any resource group.

Assign users to policies and resource groups when they are added to Amperity. This can be done using the Amperity UI or from your identity provider (IdP) when managing users with SSO group mappings.

Database permissions

A database may be associated with a single custom resource group. A custom resource group may be associated with more than one database.

Note

A database is always associated with the “All resource groups” resource group.

A database that is assigned permission to a custom resource group allows users associated with that resource group to:

  1. View that database from the Customer 360 page.

  2. View all tables in that database.

  3. Configure database exports from that database.

  4. Build segments and queries that run against that database.

  5. Design campaigns that send the results of segments to downstream workflows.

  6. Use destinations to send the results of queries to downstream workflows.

Note

Users who are associated with the “All resource groups” resource group are allowed to add and edit databases in the Customer 360 page and run Spark SQL queries against all of the data in the tenant.

To set database permissions for a custom resource group

  1. From the Customer 360 page, under All Databases, click the ellipses menu for a database, and then click Change Permissions. This opens the Permissions dialog box.

  2. Click Standard Access, and then select a custom resource group from the dropdown list.

  3. Click Save.

Multi-brand tenants

Use a combination of custom resource groups to define how teams in your organization can interact with brand databases in Amperity, where each custom resource represents a brand.

For example, a tenant with multiple brands, a global analytics team, multiple brand-specific teams, and multiple databases can:

  1. Configure a policy for the global analytics team and assign the policy to the “All resource groups” resource group.

  2. Define a custom resource group for the owners of brand A, and then configure these owners with a policy that is assigned to the brand A resource group.

  3. Define a custom resource group for the owners of brand B, and then configure these owners with a policy that is assigned to the brand B resource group.

  4. Configure the database for brand A for permissions to the custom resource group associated with brand A.

  5. Configure the database for brand B for permissions to the custom resource group associated with brand B.

This will allow members of the global analytics team to access the databases for brands A and B while ensuring that brand owners can only access their brand’s database.