Admin User Management (3.x.x and earlier) - Revision history

Carfey: /* User Rights */

2016-07-01T17:02:38Z

User Rights

← Older revision		Revision as of 17:02, 1 July 2016
Line 49:		Line 49:
	Rights are broken out into these categories: ''Default'' (read), ''Write'', ''Admin'' and ''API Access''. In addition, as starting with Obsidian 2.0, ''Default'' read access can be limited using the ''Limited Read Access'' setting.		Rights are broken out into these categories: ''Default'' (read), ''Write'', ''Admin'' and ''API Access''. In addition, as starting with Obsidian 2.0, ''Default'' read access can be limited using the ''Limited Read Access'' setting.

	''Default'' rights allow you read access to most parts of the application, with the exception of user lists and the [[System]] tab.		''Default'' rights allow you read access to most parts of the application, with the exception of user lists and the [[Admin_System_(3.x.x_and_earlier)\|System]] tab.

	''Write'' rights allow you perform most operations, with the exception of viewing and changing users, and the [[System]] tab.		''Write'' rights allow you perform most operations, with the exception of viewing and changing users, and the [[Admin_System_(3.x.x_and_earlier)\|System]] tab.

	''Admin'' rights allow you access to view and change [[Admin_System_(3.x.x_and_earlier)\|system settings]] and users.		''Admin'' rights allow you access to view and change [[Admin_System_(3.x.x_and_earlier)\|system settings]] and users.

Carfey: /* User Rights */

2016-07-01T17:02:21Z

User Rights

← Older revision		Revision as of 17:02, 1 July 2016
Line 53:		Line 53:
	''Write'' rights allow you perform most operations, with the exception of viewing and changing users, and the [[System]] tab.		''Write'' rights allow you perform most operations, with the exception of viewing and changing users, and the [[System]] tab.

	''Admin'' rights allow you access to view and change [[~~System~~]] ~~settings~~ and users.		''Admin'' rights allow you access to view and change [[Admin_System_(3.x.x_and_earlier)\|system settings]] and users.

	''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this role grants the ''Default'' read access to the admin application.		''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this role grants the ''Default'' read access to the admin application.

	''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect.		''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect.

Carfey: Carfey moved page Admin User Management to Admin User Management (3.x.x and earlier) without leaving a redirect

2016-07-01T16:55:06Z

Carfey moved page Admin User Management to Admin User Management (3.x.x and earlier) without leaving a redirect

← Older revision	Revision as of 16:55, 1 July 2016
(No difference)

Carfey at 16:50, 15 January 2016

2016-01-15T16:50:03Z

← Older revision		Revision as of 16:50, 15 January 2016
Line 55:		Line 55:
	''Admin'' rights allow you access to view and change [[System]] settings and users.		''Admin'' rights allow you access to view and change [[System]] settings and users.

	''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this ~~roles~~ grants the ''Default'' read access to the admin application.		''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this role grants the ''Default'' read access to the admin application.

	''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect.		''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect.

Carfey: /* Deleting Users */

2014-02-23T20:40:59Z

Deleting Users

← Older revision		Revision as of 20:40, 23 February 2014
Line 39:		Line 39:
	== Deleting Users ==		== Deleting Users ==

	You can also delete users from the edit page. For security reasons, you must always enter your current user password ~~to make~~ user ~~changes~~. You will be prompted to confirm the delete action.		You can also delete users from the edit page. For security reasons, you must always enter your current user password before deleting a user. You will be prompted to confirm the delete action.

	'''Note:''' Deleting users can make tracking down who made changes more difficult. Consider making a user inactive instead.		'''Note:''' Deleting users can make tracking down who made changes more difficult. Consider making a user inactive instead.

Carfey at 20:37, 23 February 2014

2014-02-23T20:37:07Z

← Older revision		Revision as of 20:37, 23 February 2014
Line 35:		Line 35:

	[[Image:AddUserEnterPassword.png]]		[[Image:AddUserEnterPassword.png]]


			== Deleting Users ==

			You can also delete users from the edit page. For security reasons, you must always enter your current user password to make user changes. You will be prompted to confirm the delete action.

			'''Note:''' Deleting users can make tracking down who made changes more difficult. Consider making a user inactive instead.

			[[Image:DeleteUser.png]]

	== User Rights ==		== User Rights ==

Carfey: /* Changing Users */

2014-02-23T20:31:49Z

Changing Users

← Older revision		Revision as of 20:31, 23 February 2014
Line 34:		Line 34:


	[[Image:~~AddUserError~~.png]]		[[Image:AddUserEnterPassword.png]]

	== User Rights ==		== User Rights ==

Carfey: /* User Rights */

2013-03-31T23:06:58Z

User Rights

← Older revision		Revision as of 23:06, 31 March 2013
Line 38:		Line 38:
	== User Rights ==		== User Rights ==

	Rights are broken out into these categories: ''Default'' (read), ''Write'', ''Admin'' and ''API Access''. In addition, ''Default'' read access can be limited using the ''Limited Read Access'' setting.		Rights are broken out into these categories: ''Default'' (read), ''Write'', ''Admin'' and ''API Access''. In addition, as starting with Obsidian 2.0, ''Default'' read access can be limited using the ''Limited Read Access'' setting.

	''Default'' rights allow you read access to most parts of the application, with the exception of user lists and the [[System]] tab.		''Default'' rights allow you read access to most parts of the application, with the exception of user lists and the [[System]] tab.

Carfey: /* User Rights */

2013-03-31T22:59:36Z

User Rights

← Older revision		Revision as of 22:59, 31 March 2013
Line 48:		Line 48:
	''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this roles grants the ''Default'' read access to the admin application.		''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this roles grants the ''Default'' read access to the admin application.

	''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that this setting ~~will not affect calls made through the REST API~~.		''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that if a user has Write or API Access, this setting has no effect.

Carfey: /* User Rights */

2013-03-31T22:58:00Z

User Rights

← Older revision		Revision as of 22:58, 31 March 2013
Line 48:		Line 48:
	''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this roles grants the ''Default'' read access to the admin application.		''API Access'' grants the user the ability to use the full [[REST API]]. In addition, this roles grants the ''Default'' read access to the admin application.

	''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected.		''Limited Read Access'' prevents the user from seeing potentially sensitive job configuration parameters. If you wish to hide these values from a user, grant them this right, otherwise leave it unselected. Note that this setting will not affect calls made through the REST API.