Miradi project data can be edited either online in Miradi Share or offline in Miradi Desktop. (Detailed work planning can be edited only in Miradi desktop.) Check-in and check-out actions ensure the data integrity of the project’s data wherever it is edited.
This article discusses the check-out / check-in actions and how they relate to data access and data integrity. See Downloading versus Checking Out a Project and Check out a Project for Editing in Miradi Desktop for more information on how to use the Download and Check Out features.
Project check-out helps ensure data integrity and control access to project content
The project check-out action:
- disables online editing of the project
- downloads a versioned project file that contains the full content of the project (except a few items such as project mapping data), and
- records who has downloaded a project file that may be edited and checked back in.
The project check-in action makes sure that the project file being uploaded back into Miradi Share is:
- the correct project*
- with full content (including private data; see more about Project Data Privacy)
- from the last user who checked the project out.
*The project file checked back in is typically the latest version that was checked out. The system notifies the user if the project file is not the latest version and asks the user if they should check it in anyway.
All of the permissions tools described in this section are used to effectively control the check-in and check-out actions. In general, a Miradi user must have Project Editor access or higher to check out a project for editing.
- Program Types and "Standalone Projects"
- Project Access State
- User Roles - Project Members and Program Members
- Project Data Privacy - Set up Redaction Rules for a Program
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.