Project Access State works together with Miradi User Roles and Program Type to help define who can view, edit, and download project information and how much project information they can view.
Project Publish State does not affect permissions or access to content but it is used to determine Team Plan subscription size.
Project Access State
Miradi projects are in one of four Project Access States. From narrowest to broadest access, the states are:
- Private (formerly Team)
- Program
- Organization
- Public
The Project Access State is set on the Miradi Access page in the PROJECT ADMIN section.
Project Access State works together with Miradi User Roles and Program Type to help define who can view, edit, and download project information and how much project information they can view. For Project Access State, generally:
- A Miradi project with “Private” access is viewable by project members only.
- A Miradi project with “Public” access is viewable by any Miradi Share visitors in the Standalone space, whether they are logged in or not, and in programs that are public. Learn more about how Program Types and Standalone Projects help define permissions.
The following Project Access States are only relevant to Miradi projects within Miradi program spaces:
- A Miradi project with “Program” access is viewable by project members plus program members.
- A Miradi project with “Organization” access is viewable by project members, program members, and Miradi users who are members of the program’s owning organization (and are logged in with their organizational email).
The primary exception to the above general rules pertains to users who are either Program Managers or Program Admins – they can view all projects in their program regardless of project access state. See also User Roles - Project Members and Program Members.
Project Publish State
A project can also define its Publish Status: Draft, Review, Publish and Archive. A project's Publish Status is set under PROJECT OVERVIEW / Miradi Project Versions.
This setting does not affect access to project information by project or program members. It is primarily used internally by project teams to track the status of their projects, and it is used to determine the size of a Team Plan subscription. Learn more about how Miradi projects count toward Team Plan size.
Learn More about Miradi Permissions
See the other articles in this section to learn more about additional tools used to manage permissions and access to data in Miradi Share:
- Program Types and "Standalone Projects"
- User Roles - Project Members and Program Members
- Project Data Privacy - Set up Redaction Rules for a Program
- Check-in and Check-out Permissions
Permissions across all dimensions of project and program access are detailed in Miradi Permissions Matrix. Note that there are two sheets in this matrix:
Comments
0 comments
Please sign in to leave a comment.