Orgs and Account Management

Account Management

Glossary of Terms

Within a project space, there are different permission/access levels. They are:

Defining Members of an Org and their Relationship

Why Add Users to an Org?

• Allows the access to the shared apps

  • This is for what the org is an authorized user for

  • If the org cannot use the app, the member cannot either

• Allow seeing the price column in the UI monitor tab and on the command line

Project Overrides for a User

• By default, when a project is created, the settings tab shows the following:

  
• The owner of the project can change these

• You may want to restrict them depending on your org policy

• Copy access

  • could be to limit how the data is handled

  • Can be changed from all members to no one

• Delete Access

  • Limit how the data is handled

  • Can be changed from Contributors and Admins to Admins only

• Download Access

  • Limit who can see the data (this would allow accessing the data outside of the platform)

  • Can be changed from all members to no one

Sharing in an Org

The org allows for the sharing

• of the same resources

  • Control the access as stated above

  • Org admins can remove and add users

• to users performing similar functions

  • Org admins can define projects and project access

  • Introduce apps and app access

Example 1: Orgs and Sharing

• Sharing projects and apps within orgs allows a group of users performing similar functions to be given the same level of access to shared resources.

• In this example, there is the org administrator, admin a, who provides view access to the project resources to the org. Additionally, admin A adds users B and C to the org, and also adds admin D to the org.

• Admin D then provides upload permissions to the project raw data, and makes the org and authorized user of the QC app. So in addition to being a convenient way to share projects and data, the org aids provide access to apps as well.

• Finally, it's very easy to revoke permissions within an org. So say for example, user C moves off the project or moves to a different institution. One of the two admins admin A or D can remove users see from the org.

Multiple Orgs

You can have multiple people in multiple orgs.

Example 2: Multiple Orgs

• Members who are working on two separate projects, and they need access to different data/ apps which have different budgets.

• the user may need to create and work on projects that are billed to two step or groups in. This is where creating multiple orgs comes in handy.

• Admin D is admin of both org and org-new because admin D needs to work within both of these orgs.

• Admin D adds user E to both org and org- new and only adds member or user F to org- new because user only needs to work within org-new.

• Looking at permissions associated with each of these users, admin A, and users B and C, have access only to org. Whereas admin D and user E have access to both org and org-new. And user F only has access to org-new.

• Orgs are flexible tools used to represent groups of users that can be used to simplify resource sharing, consolidate, billing, and associating platform work to real world billing structures.

Resources

Organization Membership Guide

Orgs Documentation

Org Management

Full Documentation

To create a support ticket if there are technical issues:

1. Go to the Help header (same section where Projects and Tools are) inside the platform

2. Select "Contact Support"

3. Fill in the Subject and Message to submit a support ticket.