Permissions - Revision history

Jen at 18:13, 22 October 2025

2025-10-22T18:13:47Z

← Older revision		Revision as of 14:13, 22 October 2025
Line 70:		Line 70:

	For a project or model that was externally shared with one (or more) of their account users, the Account admin can only assign permissions to other users if at least one of those original users was granted Admin permissions. In addition, if no one was granted Write access to the project or model, then Account admins will not be allowed to grant Write permissions to anyone, only Read and Admin.		For a project or model that was externally shared with one (or more) of their account users, the Account admin can only assign permissions to other users if at least one of those original users was granted Admin permissions. In addition, if no one was granted Write access to the project or model, then Account admins will not be allowed to grant Write permissions to anyone, only Read and Admin.

			[[Category:UserGuide\|0040_Permissions]]

Nathan: /* Assign Permissions to External Users */

2025-08-15T19:03:47Z

Assign Permissions to External Users

← Older revision		Revision as of 15:03, 15 August 2025
Line 39:		Line 39:
	To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The permissions granted for the project will be applied to all its models.		To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The permissions granted for the project will be applied to all its models.

	Admin users can ~~share~~ permissions within their ~~internal~~ account. Owner users can ~~share~~ permissions ~~with internal and external~~ accounts.		Admin users can manage permissions among users within their account. Owner users can generate tokens to grant permissions to users in other accounts.

	== Assign Permissions to External Users ==		== Assign Permissions to External Users ==
Line 60:		Line 60:
	[[File:Perms3.png\|alt=Accepting Perms Token\|frameless\|597x597px]]		[[File:Perms3.png\|alt=Accepting Perms Token\|frameless\|597x597px]]

	This user, along with any other external users, will appear in the Permissions Manager under a separate External Users table. Both the sender of the token and the receiver of the token will be able to see the External Users table. ~~Additionally~~, ~~if a user is sent a token from a second account the sender and the receiver of the token from the first account~~ will ~~be able to see the user from the second account within~~ the External Users ~~table. All~~ users who have access to a project ~~will be~~ able to see each other.		This user, along with any other external users, will appear in the Permissions Manager under a separate External Users table. The receiver will see any users on the sender's account who also have access to the content (model or project) shared. Both the sender of the token and the receiver of the token will be able to see the External Users table. If additional tokens are sent out to other accounts, all recipients will appear in the External Users permissions tables of all involved users; all users who have access to a project or model are able to see each other.

	[[File:Perms4.png\|alt=Project Details with External Users Permissions\|frameless\|599x599px]]		[[File:Perms4.png\|alt=Project Details with External Users Permissions\|frameless\|599x599px]]

Nathan: /* Assign Permissions to External Users */

2025-08-15T18:51:09Z

Assign Permissions to External Users

← Older revision		Revision as of 14:51, 15 August 2025
Line 56:		Line 56:
	[[File:Perms2.png\|alt=Project Sharing Page\|frameless\|1027x1027px]]		[[File:Perms2.png\|alt=Project Sharing Page\|frameless\|1027x1027px]]

	To gain access to the project or model, the user has to go to the Project Sharing page, copy the ~~Token~~ received by email in the dedicated field and click the ~~Submit~~ button. The new project or model should then appear in the their project/model tree.		To gain access to the project or model, the user has to go to the Project Sharing page, copy the token received by email in the dedicated field and click the submit button. The new project or model should then appear in the their project/model tree.

	[[File:Perms3.png\|alt=Accepting Perms Token\|frameless\|597x597px]]		[[File:Perms3.png\|alt=Accepting Perms Token\|frameless\|597x597px]]

Nathan: /* Assign Permissions to Internal Users */

2025-08-15T18:49:16Z

Assign Permissions to Internal Users

← Older revision		Revision as of 14:49, 15 August 2025
Line 28:		Line 28:

	= Assign Permissions =		= Assign Permissions =
	When assigning permissions to users, note that all users can see who has permissions/access to the project. This capability is also available to users from other accounts, which will be listed under "External Permissions." When making a copy of a project, there is also an option to "Copy all permissions." This will copy permissions for all internal and external users.		When assigning permissions to users, note that all users can see who has permissions/access to the project if they have any permissions to the project. This capability is also available to users from other accounts, which will be listed under the "External Permissions" table. When making a copy of a project, there is also an option to "Copy all permissions." This will copy permissions for all internal and external users.

	== Assign Permissions to Internal Users ==		== Assign Permissions to Internal Users ==
Line 38:		Line 38:

	To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The permissions granted for the project will be applied to all its models.		To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The permissions granted for the project will be applied to all its models.

			Admin users can share permissions within their internal account. Owner users can share permissions with internal and external accounts.

	== Assign Permissions to External Users ==		== Assign Permissions to External Users ==
	NOTE: For Enterprise ~~Installations~~ with a single ~~Group Account~~, all users are in the same ~~Group~~ and ~~Permission Tokens~~ are not necessary. External refers to users outside of your ~~Organization as configured in~~ PHENOM.		NOTE: For Enterprise installations with a single group account, all users are in the same group and permission tokens are not necessary. External refers to users outside of your organization's account but on the same PHENOM server.

	To assign permissions to users that do not belong to the current user's account, the user has to give them a Permissions Token. The procedure to do so is as follows:		To assign permissions to users that do not belong to the current user's account, the user has to give them a Permissions Token. The procedure to do so is as follows:
Line 58:		Line 60:
	[[File:Perms3.png\|alt=Accepting Perms Token\|frameless\|597x597px]]		[[File:Perms3.png\|alt=Accepting Perms Token\|frameless\|597x597px]]

	This user, along with any other external users, will appear in the Permissions Manager under a separate External Users table.		This user, along with any other external users, will appear in the Permissions Manager under a separate External Users table. Both the sender of the token and the receiver of the token will be able to see the External Users table. Additionally, if a user is sent a token from a second account the sender and the receiver of the token from the first account will be able to see the user from the second account within the External Users table. All users who have access to a project will be able to see each other.

	[[File:Perms4.png\|alt=Project Details with External Users Permissions\|frameless\|599x599px]]		[[File:Perms4.png\|alt=Project Details with External Users Permissions\|frameless\|599x599px]]

Nathan: /* Assign Permissions */ added section about who can see what when assigning permissions

2025-07-18T16:09:52Z

Assign Permissions: added section about who can see what when assigning permissions

← Older revision		Revision as of 12:09, 18 July 2025
Line 27:		Line 27:
	Having Owner permissions to a project or a model provide the user with Admin permissions plus the ability to delete the project or model, to change the metadata of it, and to share it with users external to their account. Owner users can assign Read, Write, and Admin permissions to internal and external users and grant Owner permissions to internal users.		Having Owner permissions to a project or a model provide the user with Admin permissions plus the ability to delete the project or model, to change the metadata of it, and to share it with users external to their account. Owner users can assign Read, Write, and Admin permissions to internal and external users and grant Owner permissions to internal users.

	= Assign Permissions =		= Assign Permissions =
			When assigning permissions to users, note that all users can see who has permissions/access to the project. This capability is also available to users from other accounts, which will be listed under "External Permissions." When making a copy of a project, there is also an option to "Copy all permissions." This will copy permissions for all internal and external users.

	== Assign Permissions to Internal Users ==		== Assign Permissions to Internal Users ==
	Users are able to assign permissions to their projects or models by using the Permission Manager on the Project or Model Details page. The table lists all the users from the same account as the current user.		Users are able to assign permissions to their projects or models by using the Permission Manager on the Project or Model Details page. The table lists all the users from the same account as the current user.

Chris: /* Assign Permissions to External Users */

2024-12-17T22:24:13Z

Assign Permissions to External Users

← Older revision		Revision as of 18:24, 17 December 2024
Line 38:		Line 38:

	== Assign Permissions to External Users ==		== Assign Permissions to External Users ==
	NOTE: For Enterprise Installations with a single Group Account, all users are in the same Group and Permission Tokens are not necessary.		NOTE: For Enterprise Installations with a single Group Account, all users are in the same Group and Permission Tokens are not necessary. External refers to users outside of your Organization as configured in PHENOM.

	To assign permissions to users that do not belong to the current user's account, the user has to give them a Permissions Token. The procedure to do so is as follows:		To assign permissions to users that do not belong to the current user's account, the user has to give them a Permissions Token. The procedure to do so is as follows:

Chris: /* Assign Permissions to External Users */

2024-12-16T14:28:30Z

Assign Permissions to External Users

← Older revision		Revision as of 10:28, 16 December 2024
Line 38:		Line 38:

	== Assign Permissions to External Users ==		== Assign Permissions to External Users ==
			NOTE: For Enterprise Installations with a single Group Account, all users are in the same Group and Permission Tokens are not necessary.

	To assign permissions to users that do not belong to the current user's account, the user has to give them a Permissions Token. The procedure to do so is as follows:		To assign permissions to users that do not belong to the current user's account, the user has to give them a Permissions Token. The procedure to do so is as follows:
	* Go to the Project Sharing page		* Go to the Project Sharing page

Nathalie at 15:11, 6 May 2024

2024-05-06T15:11:39Z

← Older revision		Revision as of 11:11, 6 May 2024
Line 20:		Line 20:
	'''If a user has Admin permissions, they are allowed to share the project or model and inherit from it'''		'''If a user has Admin permissions, they are allowed to share the project or model and inherit from it'''

	Having Admin permissions to a project or a model allows the user to create inheriting projects or models. Admin users can ~~also~~ assign permissions ~~types (provided the user has those types) of other~~ users belonging to their ~~own~~ account for this project or model		Having Admin permissions to a project or a model allows the user to create inheriting projects or models. Admin users can assign Read, Write, and Admin permissions to users belonging to their account for this particular project or model (including themselves).

	== Owner Permissions ==		== Owner Permissions ==
	'''If a user has Owner permissions, they have the same permissions as Admins, as well as some additional actions.'''		'''If a user has Owner permissions, they have the same permissions as Admins, as well as some additional actions.'''

	Having Owner permissions to a project or a model provide the user with Admin permissions plus the ability to delete the project or model, to change the metadata of it, and to share it with users external to their account. Owner users can ~~grant all permissions types (provided the user has those types) for internal users, including Owner, while the user may only~~ assign Read, Write, and Admin ~~for~~ external users.		Having Owner permissions to a project or a model provide the user with Admin permissions plus the ability to delete the project or model, to change the metadata of it, and to share it with users external to their account. Owner users can assign Read, Write, and Admin permissions to internal and external users and grant Owner permissions to internal users.

	= Assign Permissions =		= Assign Permissions =
Line 33:		Line 33:
	[[File:Perms1.png\|alt=Project Details Page Permissions Manager\|frameless\|1023x1023px]]		[[File:Perms1.png\|alt=Project Details Page Permissions Manager\|frameless\|1023x1023px]]

	To be able to share a Model, users need to have Admin or Owner permissions to it~~. The types of permissions users can grant depend on the the permissions they have to the model~~.		To be able to share a Model, users need to have Admin or Owner permissions to it.

	To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The ~~types of permissions users can grant depend on the the permissions they have to the project and its models. The type~~ permissions granted for the project will be applied to all its models.		To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The permissions granted for the project will be applied to all its models.

	~~{\| class="wikitable"~~
	~~! Current User Permissions !! Target User Permissions Options~~
	\|-
	~~\| Read + Admin \|\| Read, Admin~~
	\|-
	~~\| Read + Admin + Owner\|\| Read, Admin, Owner~~
	\|-
	~~\| Read + Write + Admin \|\| Read, Write, Admin~~
	\|-
	~~\| Read + Write + Admin + Owner\|\| Read, Write, Admin, Owner~~
	\|}

	== Assign Permissions to External Users ==		== Assign Permissions to External Users ==

Josh: /* Admin Permissions */ Update phrasing to reflect changes to Admin

2024-04-30T15:06:51Z

Admin Permissions: Update phrasing to reflect changes to Admin

← Older revision		Revision as of 11:06, 30 April 2024
Line 18:		Line 18:

	== Admin Permissions ==		== Admin Permissions ==
	'''If a user has Admin permissions, they are allowed to ~~make changes to projects~~ and ~~models themselves.~~'''		'''If a user has Admin permissions, they are allowed to share the project or model and inherit from it'''

	Having Admin permissions to a project or a model allows the user to ~~change the metadata of the project or model and~~ create inheriting projects or models. ~~They~~ can also ~~set~~ the ~~permissions~~ of other users (belonging to their own account~~) to~~ this project or model ~~up to Admin.~~		Having Admin permissions to a project or a model allows the user to create inheriting projects or models. Admin users can also assign permissions types (provided the user has those types) of other users belonging to their own account for this project or model

	== Owner Permissions ==		== Owner Permissions ==
	'''If a user has Owner permissions, they have the same permissions as Admins, as well as some additional actions.'''		'''If a user has Owner permissions, they have the same permissions as Admins, as well as some additional actions.'''

	Having Owner permissions to a project or a model provide the user with Admin permissions plus the ability to delete the project or model, and to share it with users external to their account. Owner users can grant permissions ~~up to Owner~~ for internal users and Admin for external users.		Having Owner permissions to a project or a model provide the user with Admin permissions plus the ability to delete the project or model, to change the metadata of it, and to share it with users external to their account. Owner users can grant all permissions types (provided the user has those types) for internal users, including Owner, while the user may only assign Read, Write, and Admin for external users.

	= Assign Permissions =		= Assign Permissions =
Line 34:		Line 34:

	To be able to share a Model, users need to have Admin or Owner permissions to it. The types of permissions users can grant depend on the the permissions they have to the model.		To be able to share a Model, users need to have Admin or Owner permissions to it. The types of permissions users can grant depend on the the permissions they have to the model.

	To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The types of permissions users can grant depend on the the permissions they have to the project and its models. The type permissions granted for the project will be applied to all its models.		To be able to share a Project, users need to have Admin or Owner permissions to it and to all the models it contains. The types of permissions users can grant depend on the the permissions they have to the project and its models. The type permissions granted for the project will be applied to all its models.

Josh: /* Read Permissions */ Updated image to include new editing of O perms function

2024-04-30T14:51:35Z

Read Permissions: Updated image to include new editing of O perms function

← Older revision		Revision as of 10:51, 30 April 2024
Line 10:		Line 10:
	Read permissions are unique from the other permissions types in that they are required in order to have any other permissions. For that reason, when assigning Write, Admin, or Owner permissions, Read permissions are assigned by default and can't be removed, as seen below.		Read permissions are unique from the other permissions types in that they are required in order to have any other permissions. For that reason, when assigning Write, Admin, or Owner permissions, Read permissions are assigned by default and can't be removed, as seen below.

	~~'''UPDATE IMAGE WITH OWNER COLUMN FILLED'''~~		[[File:Perms5 2.png\|frameless\|636x636px]]

	[[File:Perms5.png~~\|alt=Uncheckable Read Permissions Boxes~~\|frameless\|~~742x742px~~]]

	== Write Permissions ==		== Write Permissions ==