ReOrc docs
Get ReOrc
English
English
  • About ReOrc
  • Set up and deployment
    • Set up organization
    • Install ReOrc agent
  • Getting started
    • 1. Set up a connection
      • BigQuery setup
    • 2. Create a project
    • 3. Create data models
    • 4. Build models in console
    • 5. Set up a pipeline
  • Connections
    • Destinations
      • Google Service Account
    • Integrations
      • Slack
  • Data modeling
    • Overview
    • Sources
    • Models
      • Model schema
      • Model configurations
    • Jinja templating
      • Variables
      • Macros
    • Materialization
    • Data lineage
    • Data tests
      • Built-in generic tests
      • Custom generic tests
      • Singular tests
  • Semantic modeling
    • Overview
    • Data Modelling vs Semantic Layer
    • Cube
      • Custom Dimension
      • Custom Measure
        • Aggregation Function
        • SQL functions and operators
        • Calculating Period-over-Period Changes
      • Relationship
    • View
      • Primary Dimension
      • Add Shared Fields
    • Shared Fields
    • Integration
      • Guandata Integration
      • Looker Studio
  • Pipeline
    • Overview
    • Modeling pipeline
    • Advanced pipeline
    • Job
  • Health tracking
    • Pipeline health
    • Data quality
  • Data governance
    • Data protection
  • Asset management
    • Console
    • Metadata
    • Version history
    • Packages and dependencies
  • DATA SERVICE
    • Overview
    • Create & edit Data Service
    • Data preview & download
    • Data sharing API
    • Access control
  • AI-powered
    • Rein AI Copilot
  • Settings
    • Organization settings
    • Project settings
    • Profile settings
    • Roles and permissions
  • Platform Specific
    • Doris/SelectDB
Powered by GitBook
On this page
  • Organization level
  • Project level
  1. Settings

Roles and permissions

Roles and permissions determine a member's access to the functionalities and assets. ReOrc uses a two-tier access model with predefined roles:

  • Organization level: controls who can manage company-wide resources like team members, billing, and environment setup.

  • Project level: determines what specific actions members can perform within individual projects, such as viewing data, performing transformation, or managing project resources.

Each member can have different roles across the organization and its projects.

Organization level

  • Owner: has access to all dashboards and resources.

  • Admin: can view and edit all configuration dashboards and resources, including environment setup, projects, and users.

  • Member: can only view dashboards and have limited access to resources.

Permissions
Owner
Admin
Member

View organization information

✓

✓

✓

Edit organization information

✓

✓

Create, edit, and delete deparments and users

✓

✓

View worker list

✓

✓

✓

Deploy, join, start, stop, remove workers

✓

✓

Generate API keys

✓

✓

View destinations

✓

✓

✓

Add, edit, delete destinations

✓

✓

View integration list

✓

✓

✓

Add, edit, remove integrations

✓

✓

View project list

✓

✓

✓

Create project

✓

✓

✓

Delete project

✓ (as project owner)

✓ (as project owner)

Project level

  • Admin: can view and edit all configuration dashboards and resources of the project.

  • Developer: can view and edit assets.

  • Viewer: can view assets only.

Permissions
Admin
Developer
Viewer

View library assets (variables, macros, generic tests)

✓

✓

✓

Edit library assets

✓

✓

View packages and depedencies

✓

✓

✓

Configure packages and depedencies

✓

✓

View data design assets (sources, models, pipelines)

✓

✓

✓

Edit data design assets

✓

✓

View lineage

✓

✓

✓

Preview and build design data assets

✓

✓

View metadata

✓

✓

✓

Edit metadata

✓

✓

View Pipeline Health dashboard

✓

✓

✓

Edit pipeline jobs

✓

✓

View Data Quality dashboard

✓

✓

✓

View project settings

✓

✓

✓

Configure project connections

✓

✓

Edit project members

✓

✓

PreviousProfile settingsNextDoris/SelectDB

Last updated 15 days ago