Section: Admin
Updated: 2026-05-05

The Admin section is restricted to administrators. It contains:

• Users & Groups — team member accounts and group membership (on one combined page)
• Object Access — central view of all per-record access grants
• Permissions — module-level RBAC permission assignments per user/group
• Notifications — push notifications sent to users or groups

Navigate to Admin in the sidebar to see the sub-items.

Admin section in the sidebar — Users & Groups, Object Access, Permissions, Notifications links

Navigate to Admin → Users & Groups.

This single page shows both the Users list and the Groups list side by side (or in sections).

Users list on top, Groups list below (or side by side)

Shows all system user accounts.

Name, Email, Status (Active/Inactive), Last Login, Groups, Action buttons

Actions per user row:

• Edit — update name, email, and other account details
• Manage Groups — assign or remove this user from groups
• Manage Widgets — configure which dashboard widgets appear on this user's home screen
• Activate / Deactivate — enable or disable login access
• Delete — remove the account (only if no policy restriction)

User row — action buttons (Edit, Groups, Widgets, Deactivate, Delete)

1. Click “Add User” (or equivalent button in the Users section).
2. Enter First Name, Last Name, Email Address, and an initial password.
3. Assign the user to one or more Groups.
4. Save.

The user can then log in with their email and password.

Add User form — first name, last name, email, password, group selector

To remove access without deleting the account:

1. Click Deactivate on the user row.
2. The user can no longer log in. All records they created remain intact.

Reactivate with the Activate button when needed.

and another example row showing Activate button for an inactive user

Each user can have up to four dashboard widgets. An administrator can set these centrally:

1. Click Manage Widgets on the user row.
2. Select up to four widgets from the available list.
3. Save.

If no widgets are configured, the system shows the first four widgets the user has permission to access.

Manage Widgets modal — list of available widgets, up to 4 selectable

Groups are named sets of users. Permissions are typically assigned to groups so that everyone in the group automatically inherits the same access.

Groups list section — group name, member count, description, action buttons

Actions per group row:

• Edit — update the group name and description
• Manage Access — assign permission shortcodes to this group
• Delete — remove the group

1. Click “Add Group” in the Groups section.
2. Enter a Group Name and optional Description.
3. Save.
4. Then assign users to it via Manage Groups on the user rows, and assign permissions via Manage Access on the group row.

Add Group form — name, description fields

Navigate to Admin → Permissions.

This page manages module-level access via a hierarchical permission shortcode system. Each module and action has a unique shortcode (e.g. finance:vendor-bills, dms:queue, leads:own).

Access Permissions page — permission tree or grid showing modules as rows/nodes, user/group selector, checkboxes or toggle per permission

• Permissions are assigned to Users or Groups.
• A wildcard shortcode (e.g. finance:*) grants access to all sub-permissions under that prefix automatically.
• Permissions are additive — there is no “deny” rule. Having a shortcode means access is granted.
• Users can hold permissions both directly and via group membership. If either grants access, they have access.

1. Select the User or Group from the selector on the page.
2. Find the relevant permission shortcode in the tree.
3. Enable it (checkbox or toggle).
4. Save.

Permission assignment — user/group selector dropdown at top, permission tree below with one item being enabled

Navigate to Admin → Object Access.

Object Access is a central view of all per-record grants in the system. Normally access grants are managed from within the record itself (via the violet lock icon button on any list), but this admin page gives a complete overview.

Object Type, Object ID, Grant Type (User/Group), Grantee name, Granted By, Date, Delete button

Module-level permissions (Permissions page) control what sections a user can see. Object-level grants go one step further — they grant access to a specific record for a user who would not otherwise have access.

Example: A user has leads:own (only their own leads), but you want them to see one specific lead owned by someone else. You add an object grant for that lead record directly.

1. Select the Object Type (e.g. Lead, Contract, DMS Document).
2. Search for and select the specific record.
3. Choose Grant Type (User or Group) and select the grantee.
4. Click Grant.

Add Grant section — object type selector, object search field, user/group toggle, grantee selector, Grant button

DMS Documents, DMS Queue Records, DMS Teams Storage Paths, Vendor Bills, Sales Invoices, Payments, Vouchers, Partners, Leads, Contracts, Subscriptions.

Click the Delete button on the grant row. The grantee immediately loses the extra access.

Navigate to Admin → Notifications.

Push Notifications appear in the bell icon panel in the top navigation bar for the targeted users. They are useful for system announcements, reminders, or important alerts.

Recipient (User/Group/All), Title, Message preview, Created date, Important flag, Actions

1. Click “Add Notification” (or equivalent button).
2. Enter the Title and Message text.
3. Select the Target — All Users, a specific User, or a Group.
4. Optionally set an Expiry Date (notification disappears after this date).
5. Toggle Important if you want the notification shown in red and requiring explicit confirmation to dismiss (instead of a simple dismiss button).
6. Save.

The notification appears immediately in the target users' bell panels.

Add Notification form — title, message, target selector (All/User/Group), expiry date, Important toggle

• Normal — appear in the bell panel, user can dismiss with one click.
• Important — shown highlighted in red; user must click Confirm before the notification can be dismissed. Use for urgent or compliance-relevant messages.

Bell panel open — one normal notification and one Important notification (shown in red with a Confirm button)