Skip to main content

Roles & Permissions

Scriptix uses role-based access control (RBAC) to manage what users can do within your organization. This guide covers the available user roles.

Available Roles​

Scriptix has the following user roles:

  1. SYSOP - System Operator (back-office administration)
  2. ORGADMIN - Organization Administrator
  3. CONTRIBUTOR - Content Creator
  4. CUSTOMER - Basic User
  5. DEVELOPER - API Integration
  6. RESELLER - Reseller Management
  7. RESELLEE - Reseller's Customer
  8. TESTER - Testing Access

Role Descriptions​

SYSOP (System Operator)​

Purpose: System-level administration and back-office access

Who Has This Role:

  • Scriptix system administrators
  • Back-office support staff
  • Not a typical user role for organizations

Access:

  • Full back-office interface
  • System-wide administration
  • Customer organization management
  • System configuration

ORGADMIN (Organization Administrator)​

Purpose: Organization-level administration

Who Should Have This Role:

  • Organization owners
  • IT administrators
  • Managers who need administrative access

Capabilities:

  • Manage organization users
  • Configure organization settings
  • Access all organization documents
  • Manage folders and permissions
  • Full document creation and editing access

CONTRIBUTOR​

Purpose: Standard content creation and editing

Who Should Have This Role:

  • Team members
  • Content creators
  • Editors
  • Most regular users

Capabilities:

  • Create and upload files
  • Create transcripts and captions
  • Edit own documents
  • Access shared folders
  • Create and manage folders
  • Export documents
  • Share documents via magic links
  • Add comments to transcripts

CUSTOMER​

Purpose: Basic access

Who Should Have This Role:

  • Users with limited access needs
  • View-only users

Capabilities:

  • View shared documents
  • Limited document access
  • Basic permissions

DEVELOPER​

Purpose: API access and technical integration

Who Should Have This Role:

  • Software developers
  • Integration specialists
  • Technical team members

Capabilities:

  • API access and API keys
  • Similar document access to CONTRIBUTOR
  • Technical integration features

RESELLER​

Purpose: Reseller organization management

Who Should Have This Role:

  • Reseller account managers
  • Partner organizations

Capabilities:

  • Manage customer organizations
  • Reseller dashboard access
  • Customer billing management
  • Reseller-specific features

RESELLEE​

Purpose: Customer of a reseller

Who Should Have This Role:

  • Users in reseller customer organizations

Capabilities:

  • Access as defined by reseller
  • Organization-specific permissions

TESTER​

Purpose: Testing access

Who Should Have This Role:

  • Testing and QA purposes

Capabilities:

  • Testing-specific access

Role Assignment​

  • Users are assigned one role
  • Role determines permissions and access
  • Organization administrators can manage user roles
  • Role changes typically require administrative access

Document Access​

Folder Permissions​

Folders can have team-based permissions:

Permission Levels:

  • No Access (0) - Team cannot see folder
  • Read (1) - Team can view folder contents
  • Write (2) - Team has full access (create, edit, delete)

Folder Types:

  • Shared Folders - Accessible to all organization members
  • Private Folders - Restricted access with team permissions

Document Sharing​

Users can share documents through:

  • Magic Links - Share with anyone (requires document finalization)
  • Folder Sharing - Organize in shared folders
  • Comments - Collaborate on transcripts (CONTRIBUTOR and above)

Best Practices​

Role Selection​

Choose Appropriate Roles:

  • ORGADMIN - Limit to trusted administrators (2-3 users recommended)
  • CONTRIBUTOR - Most team members doing transcription work
  • CUSTOMER - View-only or limited access users
  • DEVELOPER - Only for users needing API access

Security​

Recommendations:

  • Assign minimum necessary permissions
  • Review role assignments periodically
  • Limit administrative access
  • Use folder permissions for additional control

Frequently Asked Questions​

Q: Can a user have multiple roles? A: No, each user is assigned one role.

Q: Who can change user roles? A: Organization administrators (ORGADMIN) can manage user roles.

Q: What's the difference between CONTRIBUTOR and CUSTOMER? A: CONTRIBUTORs can create and edit documents. CUSTOMERs have limited, view-oriented access.

Q: Can I create custom roles? A: Custom role creation depends on your plan and configuration. Contact your administrator.

Q: What role should most team members have? A: CONTRIBUTOR is appropriate for most users who need to create and edit transcripts.

Q: How many ORGADMINs should an organization have? A: 2-3 recommended for security and redundancy.

Next Steps​

Assign roles appropriately! Choose the right role for each user's responsibilities.