User Management

The User Management section centralizes all tasks related to creating accounts, assigning roles, and configuring permissions across your Ozgar AI projects. Whether you need to onboard new team members, grant them access to specific documentation, or manage system-wide settings, this interface guides you through each step with clarity and control.

1) User Roles

Ozgar AI defines both global and project-level roles to ensure precise access control:

Role	Scope	Capabilities
System Admin	Global	Full system privileges: add/remove users, assign any role, and adjust global settings.
Content Admin	Project-level	Manage all content within one or more projects: configure project settings, invite collaborators.
Documentation Revisor	Project-level	Read documentation and submit approved corrections or enhancements; changes apply immediately.
Documentation Reader	Project-level	View-only access to project documentation and dashboards.

Note: Only the System Admin role applies globally. All other roles are granted on a per-project basis and a user may hold different roles across multiple projects.

2) User Management Workflow

System Admin: Account Creation & Global Management

Access the Management → User Management page (visible only to System Admins).
Create, edit, or delete user accounts.
Assign Roles: During creation or editing, select one or more project-level roles for each project.
Enable/Disable accounts as needed to control access.

Content Admin: Inviting Collaborators

Open the Invite module within a specific project using the Sharing option.
Select an existing user by email or enter a new invitee’s email address.
Choose Role: Documentation Reader or Documentation Revisor.
Send Invitation: The user receives an email and can immediately access the designated project.

Tip: Content Admins can only invite new users for their own projects.

3) Profile Settings

Every user’s Profile page displays:

Assigned Roles: A list of projects and the roles held in each (e.g., “Project A: Content Admin”).
Global Privileges: Indication of System Admin status, if applicable.
Account Status: Enabled or disabled.

4) Example: Multiple Project Roles

Consider a user, MyUser, with these assignments:

Project A: Content Admin
Project B: Content Admin
Project C: Documentation Revisor

On MyUser’s profile, each project is listed with its respective role(s), providing clear visibility into their access levels.

5) Best Practices

Least-Privilege Principle: Grant users only the roles they need for their responsibilities.
Consistent Onboarding: Use project templates for role assignments when adding new team members across multiple projects.
Regular Audits: Periodically review user roles and disable accounts for departing employees.
Clear Invitations: When inviting users, include context about their role and expected contributions.

By following this workflow and understanding each role’s scope, you can maintain a secure, organized, and collaborative environment—ensuring every team member has the right level of access to your Ozgar AI documentation projects.