5.1 Permission-Based Access

AIUNIFY Leads uses authentication and permission checking to control access to protected workspace operations.

Many website-management routes are placed behind:

1. Authentication checks
2. Permission checks
3. Applicable license-expiration checks

5.2 Roles

The system includes role management. A role can have one or more permissions associated with it.

When an authorized administrator creates or updates a role, the selected permissions can be synchronized to that role.

5.3 Protected Administrator Role

The source includes a protected role named admin. The application prevents that role from being edited or deleted through the standard role workflow.

5.4 Module Permissions

AIUNIFY Leads provides module-oriented permission management. Authorized users can retrieve module permissions and manage how permissions are assigned to roles.

The system includes operations for:

1. Viewing permissions for a module
2. Viewing roles associated with module permissions
3. Seeding module permissions
4. Toggling role permissions
5. Bulk-updating module permissions

5.5 Staff Members

AIUNIFY Leads includes Staff Members management so organizations can provide users with individual workspace access.

The deployed routes include standard staff-member management as well as:

1. Staff-member import
2. Bulk staff-member creation

5.6 Why Different Users May See Different Functions

A user may not see or be able to operate every feature documented in this manual. Possible reasons include:

1. The user's role does not include the required permission.
2. The applicable subscription module is unavailable.
3. The applicable website limit has been reached.
4. A required website has not been selected.
5. A required AI configuration is not active.

5.7 Permission Naming

The permission system recognizes common operation types such as viewing, creating, editing, deleting, and viewing all records. These permissions are grouped by module in the management interface.

5.8 Access-Control Best Practices

1. Create individual user accounts for staff.
2. Assign users only the permissions required for their responsibilities.
3. Limit role and permission management to authorized personnel.
4. Review staff access when responsibilities change.
5. Avoid shared administrative credentials.

Best practice: Use the minimum access necessary for each role, then expand access only when the user's responsibilities require it.