Roles

Roles in Lakehousecat define the permissions and capabilities that users have within the system. The role-based access control (RBAC) system ensures that users can only access features and perform actions appropriate to their organizational responsibilities and technical expertise.

Overview

Lakehousecat uses five distinct roles to manage user access and capabilities:

• User - End users with read-only access to shared resources
• Builder - Power users who create and manage models and data sources
• Administrator - System administrators with full access
• Pending - Temporary state for inactive users
• Demo - Limited access for demonstration and evaluation

Production Roles

The three primary roles used in production environments are User, Builder, and Administrator. These roles represent the typical organizational hierarchy and technical responsibilities in a data science and analytics environment.

User Role

The User role is designed for end users who consume analytics and insights without creating or modifying underlying data structures or models.

Capabilities

Analytics Access

• View Shared Custom Models: Access to models that have been shared with their groups
• Analytics Features: Full access to analytics tools and reporting capabilities
• Charts and Dashboards: View charts and dashboards created by others or shared with them
• Data Visualization: Use visualization tools to explore shared datasets

Data Access

• Read-Only Data Access: View data through approved interfaces and models
• Shared Content: Access to content explicitly shared by Builders or Administrators
• Report Generation: Create and export reports based on available data

Interface Customization

• Language Settings: Change interface language preferences
• UI Preferences: Customize user interface elements and layouts
• Personal Settings: Manage personal profile and notification preferences

Limitations

Content Creation

• No Model Creation: Cannot design, train, or deploy custom models
• No Data Source Management: Cannot create or configure data sources
• No Dashboard Creation: Cannot create new dashboards or charts (view-only access)

System Access

• No Operations Access: Limited access to operational and runtime features
• No Administrative Functions: Cannot access user management or system configuration
• No Direct Data Manipulation: Cannot modify underlying datasets or data structures

Typical Use Cases

• Business Analysts: Consuming reports and dashboards for business insights
• Management: Accessing executive dashboards and KPI reports
• End Users: Utilizing applications built on custom models
• Report Consumers: Viewing and exporting analytical reports

Builder Role

The Builder role provides advanced capabilities for users who create and manage data science assets, models, and analytics content.

Capabilities

Data Management

• Create Data Sources: Define and configure connections to various data systems
• Manage Data Sources: Modify, update, and maintain existing data connections
• Data Quality: Implement data validation and quality checks
• Data Transformation: Design and implement data processing workflows

Model Development

• Custom Model Design: Create and architect machine learning models
• Model Training: Execute training processes and manage training data
• Model Management: Version control, deployment, and lifecycle management
• Permission Management: Control access to models and share with appropriate users

Content Creation

• Dashboard Creation: Design and build interactive dashboards
• Chart Development: Create various types of data visualizations
• Analytics Tools: Develop custom analytics and reporting solutions
• Training Data Management: Add and manage training datasets for model improvement

Collaboration

• Content Sharing: Share models, dashboards, and analyses with other users
• Team Collaboration: Work with other Builders on shared projects
• Documentation: Create and maintain documentation for models and processes

Limitations

Administrative Access

• No User Management: Cannot create, modify, or delete user accounts
• No Group Management: Cannot manage user groups or group memberships
• No Access Control: Cannot modify system-level access controls or permissions

System Administration

• Limited Settings Access: Restricted access to certain system configuration settings
• No Infrastructure Management: Cannot manage backend services or system scaling
• No Cost Management: Cannot configure billing or cost-related features

Typical Use Cases

• Data Scientists: Building and deploying machine learning models
• Data Engineers: Creating and maintaining data pipelines and sources
• Analytics Developers: Developing custom analytics solutions and dashboards
• Technical Analysts: Creating advanced analytical content and visualizations

Administrator Role

The Administrator role provides unrestricted access to all system features and is responsible for overall system management, security, and operations.

Capabilities

Complete System Access

• All System Features: Unrestricted access to every area of the platform
• Full Configuration Control: Ability to modify all system settings and configurations
• Security Management: Complete control over security policies and access controls

User and Access Management

• User Administration: Create, modify, and delete user accounts
• Group Management: Create and manage user groups and group memberships
• Permission Control: Assign roles and manage access permissions
• Access Reviews: Conduct security audits and access reviews

System Operations

• Backend Service Management: Control and scale backend infrastructure services
• Performance Monitoring: Monitor system performance and resource usage
• System Maintenance: Perform system updates, backups, and maintenance tasks

Cost and Resource Management

• Foundation Model Management: Configure and manage foundation model access
• Resource Allocation: Control compute resources and usage limits
• Cost Control: Monitor and manage system costs and billing
• Capacity Planning: Plan for system growth and resource requirements

Advanced Features

• Integration Management: Configure external integrations and APIs
• Compliance: Ensure system meets regulatory and compliance requirements
• Audit and Logging: Configure audit trails and monitoring systems

Typical Use Cases

• System Administrators: Overall system management and maintenance
• IT Managers: Infrastructure oversight and resource planning
• Security Officers: Security policy implementation and access control
• Platform Managers: Strategic platform management and cost optimization

Special Roles

Pending Role

The Pending role is a temporary state assigned to users who have been invited but have not yet activated their accounts.

Characteristics

• No System Access: Users cannot access any part of the platform
• Temporary Status: Automatically updated when user completes activation
• Administrative Oversight: Only Administrators can modify Pending users

Transition Process

1. User receives invitation email
2. Account remains in Pending state until activation
3. User clicks activation link and sets password
4. Administrator updates role to appropriate level (User, Builder, or Admin)

Demo Role

The Demo role provides limited access for demonstration, evaluation, and training purposes.

Capabilities

• Demonstration Access: Access to sample data and pre-built demonstrations
• Learning Environment: Explore system features without affecting production data
• Limited Functionality: Read-only access to demonstration content

Limitations

• No Production Access: Cannot access real organizational data
• No Content Creation: Cannot create or modify any content
• Temporary Usage: Typically time-limited access

Use Cases

• System Evaluation: Prospective users exploring platform capabilities
• Training Sessions: New user orientation and training programs
• Demonstrations: Sales and marketing demonstrations

Role Assignment Strategy

Organizational Mapping

Typical Role Distribution

Executive Management → User Role
Business Analysts → User Role
Data Analysts → Builder Role
Data Scientists → Builder Role
Data Engineers → Builder Role
System Administrators → Administrator Role
IT Security → Administrator Role

Training Requirements

User Role Training

• Basic platform navigation
• Report and dashboard usage
• Data interpretation skills
• Interface customization

Builder Role Training

• Technical Skills: Data science methodologies and tools
• Platform Proficiency: Advanced features and model development
• Best Practices: Data management and model lifecycle
• Collaboration: Working with teams and sharing content

Administrator Role Training

• System Administration: Platform management and configuration
• Security: Access control and security best practices
• Operations: Infrastructure management and troubleshooting
• Compliance: Regulatory requirements and audit procedures

Role Transition and Progression

Career Path Progression

Demo → User → Builder → Administrator

Role Change Process

1. Assessment: Evaluate user needs and technical capabilities
2. Training: Provide appropriate training for new role responsibilities
3. Gradual Transition: Implement role changes in phases when appropriate
4. Monitoring: Track user adaptation and provide additional support

Best Practices

Role Assignment

1. Principle of Least Privilege: Assign the minimum role necessary for job function
2. Regular Reviews: Conduct periodic role audits and adjustments
3. Documentation: Maintain records of role assignments and justifications
4. Training Alignment: Ensure users receive appropriate training for their roles

Security Considerations

1. Role Separation: Maintain clear boundaries between role capabilities
2. Access Monitoring: Track and audit role-based access patterns
3. Emergency Procedures: Have processes for emergency role modifications
4. Compliance: Ensure role assignments meet regulatory requirements

Organizational Alignment

1. Business Needs: Align roles with organizational structure and processes
2. Scalability: Design role structure to support organizational growth
3. Flexibility: Allow for role customization based on specific needs
4. Change Management: Plan for role evolution as organization matures

Troubleshooting

Common Issues

Role Permission Problems

• Insufficient Access: User cannot perform required tasks
  • Solution: Review role requirements and consider role upgrade
• Excessive Access: User has more permissions than needed
  • Solution: Implement principle of least privilege

Role Transition Issues

• Training Gaps: User struggles with new role capabilities
  • Solution: Provide comprehensive role-specific training
• Access Confusion: User unsure of new capabilities
  • Solution: Document role changes and provide clear guidance

Role Comparison Matrix

Feature	User	Builder	Administrator	Pending	Demo
View Shared Models	✅	✅	✅	❌	✅*
Create Models	❌	✅	✅	❌	❌
Manage Data Sources	❌	✅	✅	❌	❌
Create Dashboards	❌	✅	✅	❌	❌
User Management	❌	❌	✅	❌	❌
System Administration	❌	❌	✅	❌	❌
Interface Customization	✅	✅	✅	❌	❌

*Demo users see sample/demonstration models only