Okta can assign permissions to a user if their Role within the app assignment in Okta matches the exact name of the HubSpot permission set, including spaces and caps.
- Okta Provisioning
- HubSpot
- Syncing Roles
In most scenarios, user's roles are managed through group-based assignments, allowing Okta admins to set roles based on Okta groups rather than individual user profile attributes. This article will focus on the group-based assignments approach.
Below are the steps to follow.
Prerequisites
- Ensure provisioning has been enabled on the HubSpot app within Okta (See how to set up HubSpot Provisioning) for more details.
Step 1: Add a New Role Attribute to the HubSpot App Schema
- Navigate to Directory > Profile Editor.
- Search for the HubSpot app profile and select it.
- Click on Add Attributes and define a new role attribute with the following options:
- Data type: string array
- Display name: Roles
- Variable name: roles
- External name: roles (Please consult with the application's support to confirm what to fill in for External name)
- External namespace:
urn:ietf:params:scim:schemas:core:2.0:User - Description: (optional)
- Enum: (optional)
- Attribute type: Group (Personal only if Permission Sets will not be configured by group app assignment)
- Group Priority: Determines what to do if a user is a member of more than 1 group app assignment (see Assign attribute group priority)
- Remember that each value to be assigned and provisioned must be an exact character match with the associated Permission Sets name (see HubSpot Knowledge page Create and edit permission sets).
- Save the changes.
Step 2: Assign a Group to the HubSpot App
- Go to Applications > HubSpot > Assignments > Assign > Assign to Groups.
- Select the desired group by clicking Assign.
- Add the desired roles by clicking Add Another.
- Save the changes.
Step 3: Validate the Assignment
- Confirm that users who are part of the selected group have been successfully assigned to the HubSpot application.
- Verify that the role values were successfully pushed by checking the users' permission sets in HubSpot.
