Skip to main content
The Admin section manages user access and permissions for Auxia Console. This section covers user management, roles, and access control.

10.1 Admin Overview

What Can Admins Do?

Accessing Admin

  1. Click Admin in the sidebar
  2. Select Users & Roles

Admin Permissions Required

You need admin-level permissions (IAM_USER_VIEW, IAM_ROLE_VIEW, etc.) to access these features.

10.2 Users

User List

View all users with Console access:

Adding Users

Step 1: Click + Add User Step 2: Enter user details:
  • Name
  • Email address
Step 3: Assign role:
  • Select from available roles
  • User inherits role permissions
Step 4: Send invitation:
  • User receives email invitation
  • They set up their password

Editing Users

  1. Click user in the list
  2. Modify details:
    • Name
    • Role assignment
  3. Save changes

Removing Users

  1. Select user
  2. Click Remove/Deactivate
  3. Confirm action
  4. User loses Console access

User Status


10.3 Roles

What are Roles?

Roles are collections of permissions that define what users can do in Console.

Standard Roles

Most organizations have these default roles:

Viewing Roles

  1. Go to Admin > Users & Roles
  2. Switch to Roles tab
  3. See all configured roles

Role Details

Each role shows:
  • Role name
  • Description
  • Assigned permissions
  • Number of users with this role

Creating Custom Roles

If you have permission:
  1. Click + Create Role
  2. Enter role name and description
  3. Select permissions
  4. Save role

Editing Roles

  1. Select role
  2. Modify permissions
  3. Save changes
  4. Changes affect all users with this role

10.4 Permissions

Permission Categories

Common Permissions

Treatment Permissions: Journey Permissions: Analytics Permissions: Other Permissions:

Permission Inheritance

Users inherit all permissions from their assigned role. Multiple role assignments combine permissions.

10.5 Access Management Best Practices

Principle of Least Privilege

Grant only the permissions needed for each role:
  • Viewers don’t need edit access
  • Editors don’t need admin access
  • Analysts don’t need configuration access

Role-Based Access

Recommended Structure:

Regular Access Reviews

Periodically review access:
  • Remove departed employees
  • Adjust roles for changed responsibilities
  • Audit who has admin access

Documentation

Maintain records of:
  • Who has access
  • Why they have access
  • When access was granted

10.6 User Lifecycle

Onboarding New Users

Checklist:
  • Determine appropriate role
  • Create user account
  • Send invitation
  • User accepts and sets password
  • Verify access works
  • Provide training/documentation

Role Changes

When responsibilities change:
  1. Review current vs. needed permissions
  2. Assign new role or modify current
  3. Communicate change to user
  4. Verify new access works

Offboarding Users

When someone leaves:
  1. Immediately deactivate account
  2. Document removal date/reason
  3. Review any content they created
  4. Consider data retention needs

10.7 Security Considerations

Password Requirements

Users should:
  • Use strong, unique passwords
  • Enable multi-factor authentication (if available)
  • Not share login credentials

Session Security

  • Sessions expire after inactivity
  • Log out when finished
  • Don’t use shared computers for Console

Audit Trail

Admin actions are logged:
  • User additions/removals
  • Role changes
  • Permission modifications
Use audit logs for compliance and security review.

10.8 Troubleshooting Access Issues

”User Can’t Log In”

Check:
  1. User status is Active
  2. Email address is correct
  3. Password reset if needed
  4. Account not locked

”User Can’t See Feature”

Check:
  1. User’s role includes required permission
  2. Permission is correctly configured
  3. Feature is available in their project

”Permission Not Working”

Check:
  1. Permission is in user’s role
  2. Role is assigned to user
  3. Changes have been saved
  4. User has refreshed/re-logged

”Can’t Add User”

Check:
  1. You have IAM_USER_EDIT permission
  2. User doesn’t already exist
  3. Email format is valid

10.9 Admin FAQ

How many admins should we have?

  • At least 2 (backup for availability)
  • Not too many (security risk)
  • Recommendation: 2-3 per organization

Can users have multiple roles?

Configuration varies by organization. Ask your system administrator.

How do I know who has access?

Admin > Users & Roles shows all users and their roles. Export for reporting if needed.

What happens when I remove a user?

  • Immediate loss of access
  • Historical data preserved
  • Content they created remains

Can I restore a removed user?

Typically yes, by reactivating their account. Verify with your admin.

10.10 Requesting Access

For Users Needing Access

  1. Contact your Console admin
  2. Explain what you need to do
  3. Request appropriate role
  4. Complete any required training

Access Request Template


10.11 Admin Tools Summary


Next Section

Continue to Appendices for glossary, permissions reference, and additional resources.