Overview
Admins haveallow permissions for nearly all resources and actions in the system. This role is designed for:
- Studio owners or managers
- Users who need full control over business operations
- Personnel responsible for security and compliance
Full Capabilities
Admins can perform all actions across all six resource categories without restrictions:Agenda Management
Complete control over the studio schedule:services/permissions.py:40-47.
Use cases:
- Book appointments for any artist
- Resolve scheduling conflicts
- Block time off for multiple artists
- Generate schedule reports for accounting
Client Database
Unrestricted access to all client information:services/permissions.py:50-56.
Use cases:
- Correct client information errors
- Merge duplicate client records
- Remove test or spam entries
- Export client lists for marketing
- Access all historical notes across artists
Client deletion should be rare. Consider marking inactive instead for audit trail purposes.
Staff Management
Exclusive control over user accounts and artist profiles:services/permissions.py:59-64.
Use cases:
- Create new user accounts (admin, assistant, artist)
- Assign and change user roles
- Deactivate accounts for departed staff
- Manage artist profiles and portfolios
- Update artist availability and specialties
Financial Reports
Complete access to all financial data and operations:services/permissions.py:67-71.
Use cases:
- Review studio-wide revenue reports
- Process refunds and voids without approval
- Close cash drawer at end of day
- Export financial data for accounting software
- Audit artist commissions and payouts
Inventory Management
Full control over stock and supplies:services/permissions.py:74-80.
Use cases:
- Add new product lines
- Process supply deliveries
- Correct stock discrepancies
- Conduct physical inventory counts
- Generate supply order reports
Security and System Settings
Exclusive access to security features - no other role can access these:services/permissions.py:83-86.
Use cases:
- Configure studio business rules (hours, policies)
- Review audit logs for security investigations
- Initiate and restore database backups
- Rotate the master code periodically or after staff changes
- Manage system integrations and API keys
User Management
Admins are solely responsible for creating and managing user accounts.Creating Users
When creating a new user, admins must specify:data/models/user.py:10-14.
Role-specific requirements:
- Admin
- Assistant
- Artist
Password Management
Passwords are hashed using bcrypt before storage:services/auth.py:9-10 for password hashing implementation.
Security best practice: Require strong passwords (8+ chars, mixed case, numbers) and rotate master code quarterly.
Deactivating Users
Instead of deleting user accounts, setis_active = False to:
- Prevent login while preserving audit trail
- Retain historical data (appointments, notes, transactions)
- Allow reactivation if staff returns
services/auth.py:24).
Master Code Administration
Admins are responsible for managing the studio’s master code, which assistants use for elevated permissions.How Master Code Works
The master code is stored as a bcrypt hash in thesettings table:
services/permissions.py:149-159.
Rotating the Master Code
You should rotate the master code:- Every 90 days as a security best practice
- Immediately when an assistant leaves the studio
- After any suspected security incident
- Navigate to Security Settings (admin only)
- Use the “Rotate Master Code” action
- System generates new code and displays it once
- Immediately communicate new code to all active assistants
- Old code is invalidated instantly
Security Responsibilities
As an admin, you are responsible for:1. Access Control
- Regularly review active user accounts
- Deactivate accounts for departed staff immediately
- Ensure each person has only the minimum required role
- Never share admin credentials
2. Audit Monitoring
- Review audit logs regularly for suspicious activity
- Investigate failed login attempts
- Monitor elevated actions performed by assistants
- Track client data exports and modifications
3. Data Protection
- Initiate regular database backups
- Test backup restoration periodically
- Ensure client data is handled per privacy regulations
- Manage secure disposal of client records when required
4. System Configuration
- Keep system settings aligned with business policies
- Configure appropriate session timeouts
- Set elevation timeout appropriate for your workflow (default 5 minutes)
- Maintain integrations with payment processors and other services
Best Practices
Limit Admin Accounts
Limit Admin Accounts
Create the minimum number of admin accounts necessary. Typically 1-2 for small studios, 2-3 for larger operations.Use assistant role + master code elevation for day-to-day elevated actions.
Use Strong Authentication
Use Strong Authentication
Enforce strong password requirements:
- Minimum 8 characters
- Mix of uppercase, lowercase, numbers
- Change passwords every 90 days
- Never reuse passwords
Document Admin Actions
Document Admin Actions
Maintain a log (outside the system) of:
- When users were created/deactivated
- When master code was rotated and why
- System configuration changes
- Security incidents and resolutions
Regular Security Reviews
Regular Security Reviews
Monthly:
- Review active user accounts
- Check audit logs for anomalies
- Rotate master code
- Test backup restoration
- Review and update access policies
Example Workflows
Onboarding a New Artist
- Create artist profile in Staff Management
- Create user account:
- Role:
artist - Link to artist profile via
artist_id - Set temporary password
- Role:
- Configure artist availability and services
- Have artist log in and change password
- Artist can now:
- View their schedule
- Manage their appointments
- Upload to their portfolio
- View their financial reports
Onboarding a New Assistant
- Create user account:
- Role:
assistant - No artist linkage (
artist_id = NULL) - Set temporary password
- Role:
- Provide master code through secure channel
- Train on which actions require master code:
- Client edit/delete
- Refunds and voids
- Cash close
- Inventory adjustments
- Client data export
- Assistant can now handle front desk operations
Handling Staff Departure
- Immediately set
is_active = Falseon user account - If departing user was an assistant, rotate master code
- If departing user was an artist:
- Do NOT delete artist profile (historical data)
- Reassign or cancel upcoming appointments
- Archive portfolio if desired
- Review audit logs for any concerning actions
- Document departure in external records
Related Resources
Permissions Matrix
View complete RBAC matrix with all admin permissions
Assistant Role
Understand what assistants can do without admin approval
Artist Role
Learn about artist limitations and “own” policies
Security Settings
Configure system security and master code