ANTE User Manual

Roles

Roles define what users can see and do in the system. Each role is assigned a set of user levels (permission packs), placed in a department, and positioned in the organization hierarchy.

Overview

Open roles from the sidebar: Settings β†’ Users & Access β†’ Roles.

The Roles page lists roles in the organization. From here you can create a role, browse roles by department, and view the whole organization as an org chart.

Visibility is hierarchy-based: you only see roles at your own level and below. A role above your level does not appear in the list, the org chart, or search results β€” as if it didn't exist. Edit and Delete are only available on roles strictly below your level; a role at your own level (a peer) or above is read-only, except that a level-0 role may manage its own peers. This means two admins at different levels can see a different set of roles for the same company.

Page Layout

At the top right of the Roles page:

  • AI Assistant button (robot icon) β€” opens a chat sidebar that can list, create, update, and delete roles for you conversationally. See AI Assistant.
  • Organizational Chart button β€” opens the full-screen org chart of all roles
  • Departments button β€” opens the list of departments (role groups) that roles are organized into
  • Add Role button β€” opens the form to create a new role

Below the buttons is the roles table. You can search by Role Name or Description, and filter by Department.

Roles Table Columns

ColumnDescription
Role NameThe name of the role
DepartmentThe department (role group) the role belongs to
Reports ToThe parent role this role reports to. Shows - if top-level, or Restricted if the role does have a parent but that parent sits above your own level (so its name is withheld)
LevelThe role's level number in the hierarchy (0 = highest authority)
EmployeesHow many employees currently hold this role
Full AccessWhether the role has full access to everything (Yes / No)

Click any row to open that role's detail page.

Common Tasks

Creating a Role

  1. Click Add Role.
  2. Under Basic Information, fill in:
    • Name (required) β€” e.g., "Department Manager", "Team Lead"
    • Department (required) β€” choose from the dropdown
    • Level (required) β€” the role's rank in the hierarchy; 0 is the highest authority. You cannot assign a level above your own β€” the field starts one level below yours by default, and shows a hint with the lowest level you're allowed to enter.
    • Parent Role β€” the role this one reports to (optional; leave blank for a top-level role). The dropdown lists every role you can see across all departments, not just the selected one. Roles that can't be used as a parent β€” because they're not senior enough for the Level you entered, would create a reporting loop, or are the role itself β€” are shown greyed out with the reason (e.g. "Level 3 is not above level 3 β€” a parent role must have a lower level number").
    • Position rank β€” Executive, Director, Manager, Senior, or Staff. This is a job-title rank used when picking assignees by department; it's separate from the authority Level above.
    • Full Access β€” check this to grant the role every permission in the system
    • Description β€” a short note on the role's responsibilities (optional)
  3. Under Permissions, select the user levels to assign to this role. User levels are grouped by system module and define what actions the role can perform in each module. (You can skip this if Full Access is checked β€” the role then gets everything.)
  4. Click Create Role.

After creating, you are taken to the new role's detail page.

Viewing a Role

  1. Click a role row in the table (or click a role in the org chart).
  2. The detail page shows:
    • Basic Information β€” Name, Department, Description, Level, Parent Role, and Full Access. Parent Role shows the same Restricted treatment as the list when the parent sits above your level.
    • Statistics β€” number of employees holding the role, the number of assigned user levels you can see (with a note like "Β· 2 outside your permissions" when the role holds bundles you don't), and the total permission (scope) count from the user levels visible to you
    • Assigned User Levels β€” the user levels granted that you hold at least one permission from, each tagged with its module. If the role has user levels assigned that you hold no permissions from, the section shows "Nothing Visible To You" instead of an empty list, so it isn't mistaken for a role with no permissions at all.
    • Permissions Access β€” a per-module breakdown of the exact permissions the role grants, narrowed to what you hold

Edit and Delete only appear on this page if you're allowed to manage the role β€” see the Visibility & Permissions section below. Opening a role you can't manage shows the information read-only with no action buttons.

Editing a Role

  1. Open the role's detail page and click Edit (only shown when you can manage this role).
  2. Update the Basic Information fields β€” Name, Department, Level, Parent Role, Position rank, Full Access, Description.
  3. Adjust the Permissions (user levels) as needed.
  4. Click Save Changes.

Note: Permission changes take effect for all users with this role.

Deleting a Role

  1. Open the role's detail page and click Delete (only shown when you can manage this role).
  2. A confirmation dialog appears. If the role still has employees assigned, the dialog warns that they will lose their role assignment.
  3. Confirm to delete.

Permissions Model

Roles do not get individual checkboxes for view/create/edit/delete. Instead, permissions are bundled into user levels:

  • A user level is a named permission pack scoped to one system module (for example, an HR user level or a Treasury user level).
  • A role is assigned one or more user levels in the Permissions section.
  • The role then grants the combined permissions of all its assigned user levels.
  • Checking Full Access overrides this and grants the role all permissions β€” no user levels need to be assigned.

To manage the user levels themselves, see User Levels.

Visibility & Permissions

Roles follow the organization's Level hierarchy (0 = highest authority):

  • You can only see roles at your own level and below. A role above you is invisible everywhere β€” the table, search, the org chart, and the Parent Role picker.
  • You can only manage (Edit/Delete) roles strictly below your level. A role at your own level (a peer) is visible but read-only β€” with one exception: a level-0 role can manage its own peers, so the top tier of the hierarchy is never stuck unmanageable.
  • Where a role's parent sits above your level, the parent's name is withheld and shown as Restricted instead of being hidden as if there were no parent β€” this keeps the org chart honest about the fact that a parent exists, without exposing who it is.
  • Assigned user levels you hold no permissions from are likewise withheld from a role's detail page, with a count of how many were hidden.

Departments (Role Groups)

Roles are organized into departments (also called role groups). Click Departments on the Roles page to open the department list, where you can create, edit, and view departments and see which roles belong to each. The Department field is required when creating or editing a role.

Organizational Chart

Click Organizational Chart on the Roles page to open a full-screen, interactive chart of the role hierarchy.

The chart only draws roles at your own level and below (see Visibility & Permissions above). If a role you can see reports to a role above your level, it's shown reporting directly to "Organization" instead of being left off the chart.

  • Zoom β€” use the zoom in / zoom out / reset buttons in the header, or scroll to zoom.
  • Pan β€” click and drag an empty area to move around the chart.
  • View a role β€” click a role node to open its info dialog, where you can Edit or Delete the role.
  • Reorganize the hierarchy β€” drag a role onto another role to make it report to that role. A confirmation dialog asks you to confirm the move. Dropping a role onto the organization root makes it a top-level role.

When you delete a role from the org chart that has child roles, those child roles are reassigned to the deleted role's parent.

Role Assignment

Roles are assigned to users on the user record:

  1. Go to Users.
  2. Edit the user.
  3. Select the role.
  4. Save.

πŸ’‘ Tip: Build permissions once as user levels, then assemble roles from them. Use the org chart to keep reporting lines accurate.