Difference between revisions of "Edit permissions"

From ICA-AtoM
Jump to navigation Jump to search
 
(73 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
[[Main Page]] > [[User manual]] > [[UM-7|UM-7 Administer ICA-AtoM]] > UM-7.2 1.0.9 Edit user permissions in ICA-AtoM 1.0.9
+
[[Main Page]] > [[User manual]] > [[Administer]] > Edit permissions
  
−
When refining user permissions, it is often useful to start with the group to which the user belongs. You can refine permissions for the group, then add users to the group, all of whom will inherit the modified permissions. To lean how to refine user permissions, follow the steps in scenario 1, below. Then try some more of the scenarios listed at the bottom of this page, all of which relate to the user created in scenario 1.
+
<div class="note">
−
*You should have two or more archival institutions in your system, with several hierarchical descriptions attached and some digital objects uploaded, in order to fully test the scenarios on this page.
+
* You should have two or more archival institutions in your system, with several hierarchical descriptions attached and some digital objects uploaded, in order to fully test the scenarios on this page
−
*You can only modify the user's settings if you are logged in as an administrator. After completing the steps in each scenario, log out and log back in as the user you've been creating and modifying in order to see the results of your modifications.
+
* You can only modify the user's settings if you are logged in as an administrator. After completing the steps in each scenario, log out and log back in as the user you've been creating and modifying in order to see the results of your modifications
 +
</div>
  
−
'''Scenario 1: In a multi-repository system, add a user who can create, update and publish archival descriptions belonging to one archival institution only.'''
+
== Scenario one: Allow the public to view and download master digital objects ==
  
−
# [[Image:0_show_screen.png|500px|right|thumb|Fig.1. Default permissions for contributor group in show screen]]In the main menu bar, go to admin > groups > contributor. Click on Archival description permissions. Your screen will show the default "Grant" permissions for the contributor group - i.e. it shows you everything the user is permitted to do (see fig.1).
+
<div class="note">
−
#* Note that the Contributor group inherits some of its settings from its parent group, authenticated (which is all users who have successfully logged-in).
 
−
# [[Image:1_default.png|500px|right|thumb|Fig.2. Default permissions for contributor group in edit screen]]Click Edit. In the edit screen, you will get a better sense of the group's permission settings (see fig.2) . The contributor has the following permissions:
 
−
#* Read: Grant (inherited from Authenticated group)
 
−
#* Create: Grant
 
−
#* Update: Grant
 
−
#* Delete: Deny (inherited from Authenticated group)
 
−
#* View draft: Grant
 
−
#* Publish: Deny (inherited from Authenticated group)
 
−
#* Access master digital object: Grant
 
−
#* Access reference digital object: Grant (inherited from Authenticated group).
 
−
#** In other words, any user belonging to the Contributor group automatically has been ''granted'' the ability to read, create and update descriptions, view draft descriptions and access digital objects. However, the user has been ''denied'' the ability to delete or publish descriptions. In this Scenario 1, we would like to create a user who can create and update descriptions belonging only to a particular institution and can also publish archival descriptions belonging to the institution.
 
−
# [[Image:2_edit_group.png|500px|right|thumb|Fig.3. Modified permissions for contributor group in edit screen]]In order to restrict permissions to descriptions of a particular institution, we need to first deny the permissions to all contributors, and then add them back for the specified institution. We will do the blanket denials in the contributor group edit screen, and later add a user with permissions granted for a particular institution. To deny the permissions in the contributor group, open the edit screen and select Deny for the Create and Update permissions (See fig.3).
 
−
# [[Image:3_show_screen.png|500px|right|thumb|Fig.4. Modified permissions for contributor group in show screen]]Save the group. Your show screen should look like the screen in fig.4.
 
−
# [[Image:5_edit_user.png|500px|right|thumb|Fig.5 Add a new user]]Go to admin > users and add a new user as shown in fig. 5. Be sure to add the user to the contributor group. Click create when you're done entering the data.
 
−
# [[Image:6_user_view.png|500px|right|thumb|Fig.6]]Click on Archival description permissions. You will see the permissions that are specified in the contributor group, as in Fig.6.
 
−
# [[Image:6.1_select_repository.png|500px|right|thumb|Fig.7 Select an archival repository]]Click Edit. Click on the blue ""Permissions by archival institution" link and then the "Add archival institution" link. Select the archival institution as in fig.7.
 
−
# [[Image:7_user_edit.png|500px|right|thumb|Fig.8 Add institution-specific permissions]]You will now be able to add permissions specific to descriptions belonging to this archival institution. For Create, Update and Publish, select Grant as in fig.8.
 
−
# [[Image:8_user_view.png|500px|right|thumb|Fig.9 user view screen showing modified user permissions]]Save the record. The screen should show the modified permissions as in fig.9. To test your permissions, try logging out and logging back in as the user you created. You should be able to create, edit and publish descriptions belonging to the specified institution only, and you should not be able to delete any descriptions.
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
<br />
 
−
'''Scenario 2: Add the ability to delete the archival descriptions of the specified institution.'''
 
−
<br />
 
−
Steps: Remember that a user in the contributor group does not automatically have the ability to delete any records. To add the ability to delete archival descriptions belonging to the archival institution the user can currently edit and update, go to admin > users > Gene Roddenberry > Archival description permissions. Click Edit. For the specified institution, change the Delete permission to Grant.
 
  
 +
The default permissions in '''ICA-AtoM''' prevent the public ("anonymous" group) from viewing or download master digital objects (e.g. original TIFF images, original video files, original audio files).  By default the public ''can'' view the "reference" representation (e.g. derivative JPEG image, derivative flash video or audio file via in-browser flash player) and thumbnail version of any digital object.
  
−
'''Scenario 3: Remove the ability to create and update authority records.'''
+
</div>
−
<br />
 
−
*Permissions for authority records can be refined in some of the same ways they can be refined for archival descriptions. In a multi-repository setting it may be desirable to prevent users from creating and/or updating authority records, because one authority record may be linked to archival descriptions belonging to more than one archival institution.
 
−
*Note that users belonging to the Contributor group automatically inherit the ability to create and update authority records.
 
−
Steps: Go to admin > users > Gene Roddenberry. Instead of clicking on Archival description permissions, click on Authority record permissions. Click Edit. Under ''All authority records'', next to Create and Update, select Deny, then save the record.
 
  
 +
[[Image:Allow access to master representation.png|300px|right|thumb|Fig.3 View permissions by repository.]]
  
−
'''Scenario 4: Add the ability for the user to translate to a specified language.'''
+
This will allow the public to view or download the master objects in addition to viewing the thumbnail and reference display copies of digital objects.
−
<br />
 
−
There are two ways to grant translate permissions:
 
−
*Make the user a translator by adding him to the translator group (the same way that you made Gene Roddenberry a contributor). This means that he will be able to translate to any language.
 
−
*Instead of making the user a translator, which would allow him to translate to any language, add a language to which a user can translate. This means that he will be able to translate only to the specified language, and only those archival descriptions and authority records he is allowed to update. In this scenario, we will add the ability of the user to translate to French.
 
−
Steps: Go to admin > users > Gene Roddenberry. You should be in looking at the View user profile screen; if not, click Profile (to the left of Archival description permissions). Click Edit, then click on the blue "Access control" link. In allowed languages for translation, select French. click Save. The user will now be able to translate from any source language to French. Note that the list of languages is derived from the languages added in the settings menu. See [[UM-7.4.5|UM-7.4.5 Add or remove a language]]. Note also that you can add more languages from this list as needed.
 
  
 +
# Click Admin > Groups > Anonymous in the administrator's menu
 +
# Click the "Archival description permissions" tab
 +
# Click "Edit"
 +
# Under ''All Archival description > Access master'' click the "Grant" radio button
 +
# Click "Save"
  
−
'''Scenario 5: Remove the ability to view and download digital master objects.'''
+
<br style="clear:both" />
−
*Note that users belonging to the contributor group automatically inherit the ability to view and download master digital objects.
+
 
−
Steps: Go to admin > users > Gene Roddenberry. Click on Archival description permissions. Click Edit. Next to Access Master click Deny. Save the record. This will allow the user to view thumbnail and reference display copies of digital objects, but not to view or download the master objects. Note that if you do not wish to have any users belonging to the Contributor group viewing or downloading masters digital objects, deny permission for this activity at the level of the group - i.e. go to admin > groups > contributor and make the change at that level instead of the level of the individual user.
+
== Scenario two: In a multi-repository system, add a user who can create, update, edit, delete and publish archival descriptions belonging to one archival institution only (or whatever preferences the Administrator wants to set for the User) ==
 +
<div class=clear fix>
 +
<ol>
 +
 
 +
[[Image:singlerep_user01.png|300px|right|thumb|Fig.1. Leave group field blank. User automatically becomes an authenticated user.]]
 +
<li> When refining user permissions you can begin by creating a User, but do not assign them to a unique User group. Leave this blank and it will automatically assign the User to the parent group of authenticated (which is all users who have successfully logged-in)(See fig.1)</li>
 +
<br style="clear:both" />
 +
[[Image:singlerep_user02.png|300px|right|thumb|Fig.2.View User permissions screen]]
 +
<li>
 +
In order to restrict permissions to descriptions of a particular institution, we need to go to Admin menu > Users. Select the User you want to restrict to specific repository permissions.(See fig.2)</li>
 +
<br style="clear:both" />
 +
[[Image:singlerep_user03.png|300px|right|thumb|Fig.3 View permissions by repository.]]
 +
<li>Select information object permissions. Click Edit. Select Permissions by Repository and click Add Repository. Select Repository name from list. Click on Submit.(See fig.3)</li>
 +
<br style="clear:both" />
 +
[[Image:singlerep_user04.png|300px|right|thumb|Fig.4]]
 +
<li>Click on the circles to Grant Permissions to read, create, update, delete, view draft, publish, access master and access reference.(See fig.4)</li>
 +
<br style="clear:both" />
 +
[[Image:singlerep_user05.png|300px|right|thumb|Fig.5 View permissions for User]]
 +
<li>Click on Save.The Administrator can now view the User and their permissions in relation to a specific Repository.(See fig.5)</li>
 +
<br style="clear:both" />
 +
<li>To test your permissions, try logging out and logging back in as the user you created. You should be able to create, edit, delete and publish descriptions belonging to the specified institution only.If you want this User to have permissions to create, update and delete Authority Records and create, update and delete Taxonomies you must "grant" those as well.The default for authenticated group does not grant those permissions.</li>
 +
 
 +
</ol>
 +
</div>
 +
 
 +
== Scenario three: Add user to the contributor group as an alternative approach ==
 +
 
 +
<div class="note">
 +
 
 +
When refining user permissions, it is often useful to start with the group to which the user belongs. You can refine permissions for the group, then add users to the group, all of whom will inherit the modified permissions. Any permission that has not been "granted" by the current group (e.g., contributor, editor) or its parent group (authenticated) is considered "denied" by default. In other words the default for the system is to deny permission unless a rule explicitly grants it.
 +
 
 +
</div>
 +
 
 +
In the main menu bar, go to admin > groups > contributor. Click on Archival description permissions in the grey menu above the title bar. Your screen will show the default "Grant" permissions for the contributor group - i.e. it shows you everything the user is permitted to do. The contributor group inherits some of its settings from its parent group, authenticated (which is all users who have successfully logged-in).
 +
 
 +
Click Edit. In the edit screen, you will get a better sense of the group's permission settings. The contributor has the following permissions:
 +
* Read: Grant (inherited from authenticated group)
 +
* Create: Grant
 +
* Update: Grant
 +
* Delete: Deny (default deny)
 +
* View draft: Grant
 +
* Publish: Deny (default deny)
 +
* Access master digital object: Grant
 +
* Access reference digital object: Grant (inherited from authenticated group).
 +
 
 +
In other words, any user belonging to the contributor group automatically has been ''granted'' the ability to read, create and update descriptions, view draft descriptions, and access digital objects. However, the user has been ''denied'' the ability to delete or publish descriptions.
 +
 
 +
 
 +
</div>
 +
 
 +
== Scenario four: Remove the ability to create and update authority records ==
 +
</div class="note">
 +
Permissions for authority records can be refined in some of the same ways they can be refined for archival descriptions. In a multi-repository setting it may be desirable to prevent users from creating and/or updating authority records, because one authority record may be linked to archival descriptions belonging to more than one archival institution.
 +
 
 +
 
 +
</div>
 +
 
 +
== Scenario five: Add the ability to translate to a specified language ==
 +
 
 +
<div class="note">
 +
There are two ways to grant translate permissions to non-administrators:
 +
 
 +
* Make the user a translator by adding them to the translator group (the same way that you added a user to the contributor group). This means that they will be able to translate to any language.
 +
* Instead of making the user a translator, which would allow them to translate to any language, add a language to which a user can translate. This means that they will be able to translate only to the specified language, and only those archival descriptions and authority records they are allowed to update. In this scenario, we will add the ability of the user to translate to Dutch.
 +
 
 +
</div>
 +
 
 +
Go to admin > users > "UserName". You should be in looking at the View user profile screen; if not, click Profile (to the left of Archival description permissions). Click Edit, then click on the blue "Access control" link. In allowed languages for translation, select Dutch. Click Save. The user will now be able to translate from any source language to Dutch. Note that the list of languages is derived from the languages added in the settings menu. See [[add/remove languages]]. Note also that you can add more languages from this list as needed.
 +
</div>
 +
 
 +
== Scenario six: Remove the ability to view and download master digital objects ==
 +
 
 +
<div class="note">
 +
 
 +
Users belonging to the contributor group automatically inherit the ability to view and download master digital objects.
 +
 
 +
</div>
 +
 
 +
Go to admin > users > "UserName". Click on Archival description permissions. Click Edit. Under ''All archival descriptions'' next to Access master click Deny. Save the record. This will allow the user to view thumbnail and reference display copies of digital objects, but not to view or download the master objects. Note that if you do not wish to have any users belonging to the Contributor group viewing or downloading masters digital objects, deny permission for this activity at the level of the group - i.e. go to admin > groups > contributor and make the change at that level instead of the level of the individual user.
 +
 
 +
== Scenario seven: Add ability to create, update, and delete subject terms ==
 +
 
 +
<div class="note">
 +
 
 +
Users belonging to the contributor group do not automatically inherit the ability to create, update, and delete taxonomy terms. You can change these permissions for either the contributor group or an individual user. In this case, we will add the ability to create, update and delete subject terms to our individual user.
 +
 
 +
</div>
 +
 
 +
Go to admin > users > "UserName". Click on Taxonomy permissions (next to Authority record permissions). Click Edit. Click the blue link "Permissions by taxonomy", then click "Add taxonomy". Select Subjects as the taxonomy name from the auto-complete list. Next to Create, Update and Delete select Grant, then save the record. The user should now be able to create, update and delete subject terms but not other kinds of taxonomy terms.
 +
 
 +
 
 +
[[Category:User manual]]
 +
 
 +
__NOTOC__

Latest revision as of 11:26, 10 July 2013

Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.

Main Page > User manual > Administer > Edit permissions

  • You should have two or more archival institutions in your system, with several hierarchical descriptions attached and some digital objects uploaded, in order to fully test the scenarios on this page
  • You can only modify the user's settings if you are logged in as an administrator. After completing the steps in each scenario, log out and log back in as the user you've been creating and modifying in order to see the results of your modifications

Scenario one: Allow the public to view and download master digital objects

The default permissions in ICA-AtoM prevent the public ("anonymous" group) from viewing or download master digital objects (e.g. original TIFF images, original video files, original audio files). By default the public can view the "reference" representation (e.g. derivative JPEG image, derivative flash video or audio file via in-browser flash player) and thumbnail version of any digital object.

Fig.3 View permissions by repository.

This will allow the public to view or download the master objects in addition to viewing the thumbnail and reference display copies of digital objects.

  1. Click Admin > Groups > Anonymous in the administrator's menu
  2. Click the "Archival description permissions" tab
  3. Click "Edit"
  4. Under All Archival description > Access master click the "Grant" radio button
  5. Click "Save"


Scenario two: In a multi-repository system, add a user who can create, update, edit, delete and publish archival descriptions belonging to one archival institution only (or whatever preferences the Administrator wants to set for the User)

    Fig.1. Leave group field blank. User automatically becomes an authenticated user.
  1. When refining user permissions you can begin by creating a User, but do not assign them to a unique User group. Leave this blank and it will automatically assign the User to the parent group of authenticated (which is all users who have successfully logged-in)(See fig.1)

    2. Fig.2.View User permissions screen
  2. In order to restrict permissions to descriptions of a particular institution, we need to go to Admin menu > Users. Select the User you want to restrict to specific repository permissions.(See fig.2)

    3. Fig.3 View permissions by repository.
  3. Select information object permissions. Click Edit. Select Permissions by Repository and click Add Repository. Select Repository name from list. Click on Submit.(See fig.3)

    4. Fig.4
  4. Click on the circles to Grant Permissions to read, create, update, delete, view draft, publish, access master and access reference.(See fig.4)

    5. Fig.5 View permissions for User
  5. Click on Save.The Administrator can now view the User and their permissions in relation to a specific Repository.(See fig.5)

  6. To test your permissions, try logging out and logging back in as the user you created. You should be able to create, edit, delete and publish descriptions belonging to the specified institution only.If you want this User to have permissions to create, update and delete Authority Records and create, update and delete Taxonomies you must "grant" those as well.The default for authenticated group does not grant those permissions.

Scenario three: Add user to the contributor group as an alternative approach

When refining user permissions, it is often useful to start with the group to which the user belongs. You can refine permissions for the group, then add users to the group, all of whom will inherit the modified permissions. Any permission that has not been "granted" by the current group (e.g., contributor, editor) or its parent group (authenticated) is considered "denied" by default. In other words the default for the system is to deny permission unless a rule explicitly grants it.

In the main menu bar, go to admin > groups > contributor. Click on Archival description permissions in the grey menu above the title bar. Your screen will show the default "Grant" permissions for the contributor group - i.e. it shows you everything the user is permitted to do. The contributor group inherits some of its settings from its parent group, authenticated (which is all users who have successfully logged-in).

Click Edit. In the edit screen, you will get a better sense of the group's permission settings. The contributor has the following permissions:

  • Read: Grant (inherited from authenticated group)
  • Create: Grant
  • Update: Grant
  • Delete: Deny (default deny)
  • View draft: Grant
  • Publish: Deny (default deny)
  • Access master digital object: Grant
  • Access reference digital object: Grant (inherited from authenticated group).

In other words, any user belonging to the contributor group automatically has been granted the ability to read, create and update descriptions, view draft descriptions, and access digital objects. However, the user has been denied the ability to delete or publish descriptions.


Scenario four: Remove the ability to create and update authority records

Permissions for authority records can be refined in some of the same ways they can be refined for archival descriptions. In a multi-repository setting it may be desirable to prevent users from creating and/or updating authority records, because one authority record may be linked to archival descriptions belonging to more than one archival institution.


Scenario five: Add the ability to translate to a specified language

There are two ways to grant translate permissions to non-administrators:

  • Make the user a translator by adding them to the translator group (the same way that you added a user to the contributor group). This means that they will be able to translate to any language.
  • Instead of making the user a translator, which would allow them to translate to any language, add a language to which a user can translate. This means that they will be able to translate only to the specified language, and only those archival descriptions and authority records they are allowed to update. In this scenario, we will add the ability of the user to translate to Dutch.

Go to admin > users > "UserName". You should be in looking at the View user profile screen; if not, click Profile (to the left of Archival description permissions). Click Edit, then click on the blue "Access control" link. In allowed languages for translation, select Dutch. Click Save. The user will now be able to translate from any source language to Dutch. Note that the list of languages is derived from the languages added in the settings menu. See add/remove languages. Note also that you can add more languages from this list as needed.

Scenario six: Remove the ability to view and download master digital objects

Users belonging to the contributor group automatically inherit the ability to view and download master digital objects.

Go to admin > users > "UserName". Click on Archival description permissions. Click Edit. Under All archival descriptions next to Access master click Deny. Save the record. This will allow the user to view thumbnail and reference display copies of digital objects, but not to view or download the master objects. Note that if you do not wish to have any users belonging to the Contributor group viewing or downloading masters digital objects, deny permission for this activity at the level of the group - i.e. go to admin > groups > contributor and make the change at that level instead of the level of the individual user.

Scenario seven: Add ability to create, update, and delete subject terms

Users belonging to the contributor group do not automatically inherit the ability to create, update, and delete taxonomy terms. You can change these permissions for either the contributor group or an individual user. In this case, we will add the ability to create, update and delete subject terms to our individual user.

Go to admin > users > "UserName". Click on Taxonomy permissions (next to Authority record permissions). Click Edit. Click the blue link "Permissions by taxonomy", then click "Add taxonomy". Select Subjects as the taxonomy name from the auto-complete list. Next to Create, Update and Delete select Grant, then save the record. The user should now be able to create, update and delete subject terms but not other kinds of taxonomy terms.


Retrieved from "https://wiki.ica-atom.org/index.php?title=Edit_permissions&oldid=13650"