Skip to main content

Organizations and Projects (Rill Cloud)

Once a project is ready to be deployed onto Rill Cloud, as an admin, you will need to manage your organization, project, and user access. Depending on where you set this access, the permissions can vary. Please see our Roles and Permission page for more details.

Organization​

An Organization in Rill is the parent management object and encompasses how your team or organization interfaces with Rill Cloud. Organizations are designed to hold the differnet components of your Rill project. Projects exist within an organization, which itself contains sources, models, dashboards, and other resources that belong to your standalone Rill projects.

If you'd like to create, edit, modify, or delete an organization, you can do this either via the CLI or UI.

CLI​

rill org

UI​

a

tip

Access to Rill can be granted on the organization level.

Project​

A project is a single deployed instance from Rill Developer (or what we refer to as a Rill project). Each project can be connected to one GitHub repository. Once you have deployed a project to Rill Cloud, you can make changes to it via the CLI or the UI.

CLI​

Managing a project includes the project itself and all components or resources that belong to the project. Via the CLI, you can make changes to the project's properties such as description, GitHub branch, etc using the following:

rill  project

Updating the deployment​

Your project on Rill Cloud will automatically redeploy every time you git push changes to Github. To manually refresh data sources without pushing code changes (or redeploying your project), run the following command:

rill project refresh

Checking deployment status​

In case you need to check the project status via the CLI, you can run the following:

rill project status

Deploying from a branch other than main​

A branch from which continuous deployment is setup can be changed while editing the project. To change the branch, run the following command:

rill project edit

UI​

Checking deployment status​

After deploying to Rill Cloud, you will be navigating to the status page. Here you will be able to see your component's status and if there are any issues with loading or parsing.

img

Deploying from a branch other than main​

If you have already setup your connection to GitHub, you can edit the branch from where the project is deployed from.

img

tip

Access to Rill can be granted from the project level.

Make a project public​

Projects on Rill Cloud are private by default. To make a project's dashboards publicly accessible without authentication, run:

rill project edit --public=true
Avoid Sharing Private Data

Warning: If you make a project public, make sure it does not expose any confidential data.

Reference: Walking through access levels​

In the following example, you can see the different levels of access to Rill via the organization, project-specific access, user group and user privileges.


Key things to note​

  1. There are three levels of access: organizations, projects, and groups.
  2. User groups can only exist within an organization.
  3. User groups permissions can either be added for the organization as a whole, or specific projects.
    • rill usergroup create [--project project_name]
  4. User groups can currently only be applied to users within the organization.
    • In the above diagram, pink_user can not be added to a user group.
  5. All users added to an organization must have at least viewer privilege.
    • In the above diagram, yellow_user is redundant as there's already viewer access.