Identity and access management (Content)

The identity and access management (IAM) functionality allows you to control user access rights to view and make changes in specific parts of Bloomreach.

📘

See Identity and access management (Discovery) for a list of user roles for Discovery.

User interface

The user management UI allows for the creation, modification, and deletion of users and contains admin roles to assign and revoke permissions to users. Typically, these UI features will be managed by an admin who is either a business user or an IT admin at your organization. The admin will have access to the user management UI and can make changes to users.

The UI allows for the following:

1. Creation of new users
2. Management of user data
3. Resetting of passwords
4. Role assignment
5. Deletion of users

Add a new user

1. Navigate to Setup in the left nav
2. Click on User management
3. Click on the Add New User button
4. Fill in the user's information, including e-mail address, and select their site access and roles
5. Click on Add New User to complete the process

Manage an existing user

1. Navigate to Setup in the left nav
2. Click on User management
3. Click on the Manage dropdown in the Action column
4. In the dropdown, you will see three choices:
   1. Manage User: change or remove assigned roles and site access
   2. Resend Invitation Email: reset the password for the user and send a password reset e-mail automatically to the e-mail address listed for that given user
   3. Delete User: remove the user completely from access to Bloomreach. This action is not reversible.

User roles for Content

The following roles for Content are supported in IAM. These are the roles that an IAM admin can assign to Users. You will only see the roles that are reflective of the Bloomreach products you have integrated on. For example, if you are not integrating Insights and are not an Insights customer, you will not see the "Insights User" role and will not be able to assign this role to anybody. 

IAM site hierarchy 

Bloomreach customer hierarchy is Parent Organization → Account → Site. 

A user can be assigned a role at any node in this hierarchy: they can be assigned a role at the Parent Organization node, the Account node, or the Site node.  If a role is given to a node at a higher level, it is propagated to all levels below it. For example, if user A was assigned the "Insights User" role at the Organization node, they would also be an "Insights User" at the Site node. However, if they were assigned "Insights User" at the Site node, they would not have the "Insights User" role at the Organization node.

Most customers will choose to assign users roles at the Account node. If the customer has a multisite account, they may choose to give users permission at the Organization level (for wider permissions) or at the Site level (for more scoped permissions). 

The following are more detailed descriptions of the concepts in IAM.