# Orgs and Account Management
### Account Management
#### Glossary of Terms
User
A single person that is utilizing the platform
Org
Collection of users. They are either admin or member level
Permissions
Gives the user the ability to work on the platform within the scope of what they are needing to access
Project
means of enabling users to collaborate by providing them with shared access to specific data and tools.
#### Within a project space, there are different permission/access levels. They are:
{% tabs %}
{% tab title="Viewer" %}
Most restrictive: view the project, move and copy data across projects.
{% endtab %}
{% tab title="Uploader" %}
View and Create folders and modify metadata
{% endtab %}
{% tab title="Contributor" %}
Uploader AND run executions
{% endtab %}
{% tab title="Admin" %}
Contributor AND change permissions for users, project ownership, and deletion
{% endtab %}
{% endtabs %}
#### Defining Members of an Org and their Relationship
{% tabs %}
{% tab title="Org" %}
* is used to represent a group of users
* Can be used to simplify the sharing of projects, apps, and billing
* Have members and admins
{% endtab %}
{% tab title="Admin" %}
control the access to
* billable activities
* shared apps
* shared projects
{% endtab %}
{% tab title="Members" %}
are either allowed or not allowed to access
* billable activities
* shared apps
* shared projects
{% endtab %}
{% tab title="Users" %}
* is a single user on the platform
* can be an org admin or an org member
* they can also just be added to project and NOT a member of an org, but they will not see pricing or have access to org specific options unless part of the project itself.
* holds one of 4 types of permissions to a project
{% endtab %}
{% endtabs %}
#### 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](https://documentation.dnanexus.com/user/organization-member-guide)
[Orgs Documentation](https://documentation.dnanexus.com/getting-started/key-concepts/organizations)
[Org Management](https://documentation.dnanexus.com/admin/org-management)
[Full Documentation](https://documentation.dnanexus.com/)
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.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://academy.dnanexus.com/billing-access-and-orgs/account_management_and_orgs.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.