Managing Projects

On the Documents page:

1. Select Create then in the dropdown, select Project.

   The creator of the Project is automatically assigned the role of Project Administrator upon creation of the Project. This may not be undone.

2. Supply a name and description for the Project.
3. Select a Permission scheme from the list.
4. Create the Role map by selecting a User or Team and then an associated Role from the drop down menus:

   

5. Click Add to add each User/Role entry. The entry will appear in the lower portion of the dialog.

   To enter individual users (via email address), the user must first be a part of the company domain as defined under Enterprise/Company settings > Users. Teams must also be pre-defined under Enterprise/Company settings > Teams.

6. Repeat steps 4 and 5 to create additional entries in the Role map.
7. Click OK to save the Project state, (or click Cancel to close without creating the Project).

A change to a Permission scheme affects all Projects that reference that Permission scheme.

The option to clone an existing project provides an easy way to create a new project with the same permission scheme, settings, users, and role map as an already-existing document. On the documents page:

1. Under Projects, right-click on the project you wish to clone.
2. A context menu appears:

   

3. Click Clone project...
4. A dialog box appears, already filled out with the same properties from your previous project.
5. Click OK in the bottom right corner to create your cloned project.

Modifying a project’s Permission scheme, role map, name, and description requires that the user have Share permission.

Removing users or teams

On the Documents page:

1. Right-click the Project in the list and select Edit project.
2. Click the X next to the role in the Role map to delete an unwanted entry from the Role map. Add role map entries by selecting users and/or teams and the associated Role as described above.

Changing permission scheme

On the Documents page:

1. Right-click the Project in the list and select Edit project.
2. Use the drop down to select a new Permission scheme.

   When a new Permission scheme is selected, all users and teams are removed from the Project role map (except the original Project Administrator) thus resetting the role map.

3. Make a new role map by specifying users and roles as described above.
4. Click OK to save changes, or click Cancel to close the dialog without saving any changes.

Projects are basically containers for documents allowing you to group them; the permissions you apply to the Projects affect all documents inside the Project as well. Folders also hold documents and other folders, but can not hold Projects. Projects are always created at the root level. Projects can include folders and sub-folders. The permissions on folders within Projects are inherited from the permissions assigned to the Project.

Since permissions are applied to Project via Permission schemes and those permissions apply to all documents and folders within the Project, when you move documents or folders into and out of Projects, the permission scheme assigned to the Target project become the permissions assigned to the document and folders moved.

The action of moving documents and folders into and out of Projects itself requires the appropriate permissions:

• To move a document or folder within a Project requires Edit permission on the document or folder's Project. One example of moving a document within a Project is moving it from one folder to another within the same Project.
• To move a document or folder into or out of a Project requires full permission on both the source Project and the target project. Full permission includes: Delete, Share, Edit, View, Link, Copy, Export and Comment.

Since the permissions to the documents within a Project are assigned at the Project level, moving a document into or out of a Project may result in a change of permissions on the document. (See below for more information.)

1. Select a document in the Documents list.
2. Right-click on the document name on the Documents page. (Or select multiple documents and then right-click.)
3. Select Move to... from the menu.
4. Select a project.

   Click Show details to see which document/s you are moving.

5. Click Move here to move the document/s, or click Cancel without executing the move operation.

To move a document out of a project:

1. Select the document (or documents) within the project.
2. Right-click and select Move to... from the menu.
3. Use the breadcrumbs at the top of the dialog to navigate to the desired level, project, or folder.
4. Click Move here to move the document/s, or click Cancel without executing the move operation.

When copying a workspace in a project (thereby creating a new document), you need edit permission on the project in order for the copy to be placed in the same project as the original document. If you do not have edit permission on the project, the copy is placed at the root level of your Onshape account which is your Company name. A blue notification is displayed at the top of the window upon successful copy that it has been created at the root level.

• Use the drag and drop method of moving documents and folders into and out of other folders and projects.
• There is no way currently for administrators to channel users into creating documents in certain projects.
• Projects are listed in the Company name page filter.
• You can only move a document out of a Project if you have Share permission on the Project and into another Project if you have Edit permission on that Project.

Projects are collections of documents that are associated with Permission schemes (Project roles and Permission pairs) which apply permissions to groups of users. The permissions associated with a group of users for a project apply to all documents inside the project.

Users with the Edit permission are free to create documents: inside of or outside of Projects with which they have been associated as long as they have the proper permissions to the Project. Users are associated with Projects by way of the Permission scheme that is associated with the Project.

• A document can only belong to one project.

• Users with edit permissions on a project can:

  • Create documents and folders in the project.

  • Move documents into and out of the project.

Project definitions contain this information:

• Name
• Description
• Permission scheme and associated users
• Users and the roles they may act in

A change to a Permission scheme affects all Projects that reference that Permission scheme.

Modifying a project’s Permission scheme, Project roles, name, and description requires that the user have Reshare permission. Adding a document to or removing a document from a Project requires that the user have Edit permission.

Projects definitions can be administered or otherwise edited only on a browser.

Permissions

When a Project is created, the creator is automatically placed into the Project Administrator role, which grants full permission to that user. A project must always have a project admin (or someone with a similar full-permission role) to prevent users from getting into a situation where they are locked out of their project).

Changing from one Permission scheme to another on a project automatically remaps users whose roles exists in both schemes (the original Permission scheme and the new one being assigned).

The dialogs in this process are ‘draft’ which means you must confirm the action in order for it to be executed. If you close the dialog without saving or exiting properly, all changes are discarded.

Projects are collections of documents that are associated with Permission schemes (Project roles and Permission pairs) which apply permissions to groups of users. The permissions associated with a group of users for a project apply to all documents inside the project.

Users with the Edit permission are free to create documents: inside of or outside of Projects with which they have been associated as long as they have the proper permissions to the Project. Users are associated with Projects by way of the Permission scheme that is associated with the Project.

• A document can only belong to one project.

• Users with edit permissions on a project can:

  • Create documents and folders in the project.

  • Move documents into and out of the project.

Project definitions contain this information:

• Name
• Description
• Permission scheme and associated users
• Users and the roles they may act in

A change to a Permission scheme affects all Projects that reference that Permission scheme.

Modifying a project’s Permission scheme, Project roles, name, and description requires that the user have Reshare permission. Adding a document to or removing a document from a Project requires that the user have Edit permission.

Projects definitions can be administered or otherwise edited only on a browser.

Permissions

When a Project is created, the creator is automatically placed into the Project Administrator role, which grants full permission to that user. A project must always have a project admin (or someone with a similar full-permission role) to prevent users from getting into a situation where they are locked out of their project).

Changing from one Permission scheme to another on a project automatically remaps users whose roles exists in both schemes (the original Permission scheme and the new one being assigned).

The dialogs in this process are ‘draft’ which means you must confirm the action in order for it to be executed. If you close the dialog without saving or exiting properly, all changes are discarded.