In this article
By assigning an end user to one or more nodes in Hierarchy Management, and assigning a role to that user, the user can get access to surveys "created in" the relevant parts of the hierarchy. Access to these surveys will come in addition to surveys that the user created himself, and surveys that survey creators have explicitly shared with the user.
Connecting End Users to Hierarchy Nodes (for Survey Creation)
The role-based access model depends on end users being created from contacts, so that Pulse knows which hierarchy node each user "belongs to".
Note: This is not the same as a node assignment. A user can belong to only one node, but can be assigned to zero or more nodes.
When a user creates a survey, Pulse will create a new record in a custom table in the hub, called Surveys. The record contains the hierarchy id and hierarchy node id that the user was associated with at the time the survey was created. Note that the survey’s hierarchy node id will not be updated even if that user is later moved to another hierarchy node.
Details on how the hierarchy node is resolved can be found below.
The records in the Surveys table are the basis of Data Engine queries to find the surveys a user should have access to, based on node assignments. Records where the hierarchy node id is blank are created either by end users who don’t have an association to a node, or by professional users.
Hierarchy Node Assignments
End users can be assigned to nodes in Hierarchy Management. Refer to the separate Hierarchy Management documentation for further details.
Node assignments are synced to a custom table in the hub, called NodeAssignments. This enables Pulse to use them in Data Engine queries, and "join" them with the Surveys table.
User Roles
User roles must be added to a custom table in the hub, in a dataset named Authorization, with the name UserRoles. This table must be created manually by the program maintainer.
Unlike the Surveys and NodeAssignments tables, the UserRoles table is actually the "source of truth" for role data.
Once you have created the table, you can upload a spreadsheet that has two columns: Username and Role. The Username column should contain the end user username, and the Role column should contain the role (hr or manager, described below).
To add, remove or change roles, you just upload a new version of the spreadsheet.
Note: Both usernames and roles are case-insensitive.
Manager - has Report access to surveys created on direct child nodes of the hierarchy node(s) the user has been assigned to (i.e., exactly 1 level below their node assignments).
HR - has Manage access (i.e., full permissions) to surveys created on the hierarchy node(s) the user has been assigned to, and all descendant nodes. The HR user can access all surveys regardless of their state (Draft, Live, Closed), and can make any change to the survey that the survey owner can (including commit and delete).