This article discusses Org Admins and project Admins, including what these types of Admins can do and how to become an Admin. 

Admins in Filevine have access to additional capabilities like inviting new members, Advanced tools, changing members’ team status, and more. Org Admins and project Admins exist separately, meaning that a user can be an Org Admin without being a project Admin and vice versa. Org Admins have Org-level permissions like Advanced tools, while project Admins have project-specific permissions like access to locked fields in a project and the ability to adjust users’ statuses for the project. 

Org Admins
Project Admins

Org Admins

Org Admins have Org-level permissions like default access to the Mailroom. Org Admin status is also necessary for access to some Advanced Tools like the Customs Editor and Mass Update Permissions tools. Org Admins also have control over other users’ team status at the Org-level, meaning that an Org Admin could make a user a follower on all projects in an Org, for example. 

Org Admins:

• enables the Org’s setup page.
• can change any user’s team status on an Org-level basis.
• will have access to the Mailroom by default.
• is eligible to use the Advanced tools.
• will have access to all data created in a cross-project Fusion report, regardless of project-by-project permissions.

Becoming an Org Admin

Becoming an Org Admin requires an existing Org Admin to designate you as an Org Admin. An Org Admin can designate another Org Admin by following the steps below.

1. Select Setup > Org > Members. Navigate to the “Members” tab in Setup by clicking on the hamburger menu in the top left corner and selecting “Setup” from the dropdown. In the lefthand side menu, select “Orgs.” In the tabs across the top of this page, select “Members.”
   
2. Navigate to Org Admin tab in the card. Click on the user card of the user you’d like to make an Org Admin to open it. In the opened card, select the “Org Admin” tab.
   
   
3. Toggle on “Make [User] an Org Admin.” Click on the toggle to the right of “Make [User] an Org Admin” and then click the blue “Update” button. In the popup, click “Yes, Update.”

Project Admins

Project Admin status enables access to certain permissions on a project level. For example, a project Admin can remove some saved items, manage team status, and more.

Project Admins can, for any project where they have project Admin status:

• change a user’s team status.
• invite outside parties and clients into the project.
• enable and disable texting.
• remove a saved collection item.
• remove a saved document from the Docs section.
• edit any field that has been locked for project admin access only.
• pin (and unpin) items to the project's activity section.
• utilize the "Move To" option for notes and texts in the activity section.

Becoming a Project Admin

Becoming a project Admin requires another project Admin, who will designate you as a project Admin. You can be designated as a project Admin for a specific project or for all new projects.  Alternatively, Org Admins can also make themselves a Project Admin on projects using the settings in the Members > Org section or the Mass Update Permissions Advanced tool.

To become a project Admin for a specific project, another project Admin should follow the steps below. 

1. Navigate to the project. In the “Search for a project” text box in the top right corner, search for an select the project.
2. Select Team and find user card. In the lefthand menu of the project, select the “Team” section. Once in this section, search for the user you’d like to make a project Admin. You may need to click through Followers, Collaborators, and Guests to find them.
   
   
   
3. Open card and click “Make Admin.” Click on the user card to open it, and click on “Make Admin” in that window.
   
   
   
4. View changes. You can confirm the change by closing the window and viewing the user card. The user will now have a “Project Admin” tag in their card.
   
   

Org Admins also have the option to make a user a project Admin on all projects going forward, using the Org > Members tool.