Overview
The User Management module streamlines the process of adding and managing users on the Capillary platform. Brands can manage all users within the organization and their permissions using this module.
Features
The following actions can be performed:
- Add up to 10 users from the UI using individual email addresses
- Add or update up to 50 users via bulk upload
- View or search the user listing with important details
- Export the users' list
- Remove one or more users from the organization
- Support for different types of users: Standard, Admin, and Org Owner
- Predefined Standard Permission Sets for creating users
- List and create new Permission Sets with a categorized module-wise view
Note
If a user is created in the old flow, their user type won’t be mapped in the new UI; it will default to Standard User and needs to be updated explicitly.
Accessing the Module
To access, navigate to Organization settings > Organization Setup > User Management.
Types of Users in the Organisation
The users in an organisation are classified into three types:
- Standard user
- Admin User
- Organisation owner
Standard User
A Standard User is an individual with restricted access within the organisation. A standard user has the following limitations:
- Limited access to the organisation and its subsets, including specific stores, concepts (org units), and zones.
- Can only view their own profile.
- Does not have access to manage other users or their access permissions.
- Access must be assigned explicitly by an Org Owner or Admin User.
Admin User
Admin Users are explicitly created by organisation owners to handle specific tasks and perform duties on their behalf. Admin Users have all the capabilities of Standard Users, with additional abilities to:
- Create, view, and delete Standard Users.
- Provide access permissions to Standard Users.
Organisation Owner
An organisation owner (org owner) will have full authority over an organisation and all the modules and can add other standard or org owner-type users. An organisation must have at least one org owner.
The org owners can perform the following:
- Create more Org owners if required.
- Create, View, Update, and Delete any users/permissions. By default, the org owner can access all Standard and custom permissions.
Terms and Definitions
The below table lists the terms and definitions used in this documentation.
| Term | Definition |
|---|---|
| User | A user is anyone with access to the Capillary platform, capable of taking actions across various modules including Loyalty, Member Care, Engage+, and more. |
| User types | A user type refers to a predefined set of permissions and access rights assigned to a user within an organisation's system or platform. For more information, refer to the section User Types. |
| Accessible Entities / Resources | Accessible entities, also known as resources, specify the subsets within an organisation that are accessible to the user. These entities include stores, organisational units (concepts), and zones |
| Access team | The access team refers to the internal Capillary team managing users across every org on our platform. |
| Permission | The permissions define what data and functionality a user can access within a system. RBAC (Role-Based Access Control) operates on the principle that users should have access only to resources necessary for their role (principle of least privilege). This ensures that users, like Customer Service Representatives (CSRs) using Member Care, have the specific permissions required—such as searching for a customer, viewing profiles, and modifying identifiers to perform their tasks effectively. Individual permissions cannot be assigned directly to a user without being part of a defined permissions set. |
| Permission set | A permissions set, also known as a permissions bundle or access group within our framework, is a collection of permissions that can be assigned to a user. For instance, when configuring access for a CSR using Member Care, we aggregate relevant Member Care-related permissions into a set or group and assign it to the user. For more information, refer to the section Permission sets. |
| User role | A user role is an assigned designation of the user provided when adding users in bulk. |
Updated about 2 months ago