2023:Permission Sets: Difference between revisions
No edit summary |
No edit summary |
||
| Line 27: | Line 27: | ||
You can also restrict what actions an individual can take while working in Grooper. If you want to avoid someone accidentally deleting a batch or clicking cut instead of copy, you can restrict those actions. | You can also restrict what actions an individual can take while working in Grooper. If you want to avoid someone accidentally deleting a batch or clicking cut instead of copy, you can restrict those actions. | ||
===Adding Permission Sets=== | |||
There are two parts to configuring permission sets: granting/restricting page access and granting/restricting permissions. | |||
<tabs style="margin:20px"> | |||
<tab name="Page Access" style="margin:20px"> | |||
====Page Access==== | |||
The first part of configuring permission sets is configuring what groups can have access to which pages in Grooper. By default, everyone has access to every page in your repository. For example, if you would like users to only have access to the "Batches" and "Tasks" pages, we can do that here. | |||
{|cellpadding=10 cellspacing=5 | {|cellpadding=10 cellspacing=5 | ||
|style="width:40%" valign=top| | |style="width:40%" valign=top| | ||
| Line 70: | Line 81: | ||
| | | | ||
[[File:2023-Permission Sets - Creation 07.png]] | [[File:2023-Permission Sets - Creation 07.png]] | ||
| | |} | ||
|valign=top| | |||
# | Now that we have restricted the pages we wish the "Users" group to have access to, take a look at the next tab to learn how to restrict what "Users" can do in those pages. | ||
</tab> | |||
<tab name="Permissions" style="margin:20px"> | |||
====Permissions==== | |||
{|cellpadding=10 cellspacing=5 | |||
|style="width:40%" valign=top| | |||
# At the bottom of the properties list on the right, there are three sets of permissions you can apply to the selected Permission Set: | |||
#* '''''Node Permissions''''' | #* '''''Node Permissions''''' | ||
#* '''''Attachment Permissions''''' | #* '''''Attachment Permissions''''' | ||
| Line 111: | Line 132: | ||
| | | | ||
[[File:2023-Permission Sets - Creation 14.png]] | [[File:2023-Permission Sets - Creation 14.png]] | ||
|} | |||
</tab> | |||
| | [[Adding Permission Sets|Click here to return to the top of the section]] | ||
</tabs> | |||
Revision as of 13:45, 17 March 2023
| WIP |
This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly. This tag will be removed upon draft completion. |
Add Permission Sets to Grooper 2023
In this article we will show you how to add and update permission sets to access different areas of a repository in Grooper 2023.
| ‼ |
New Functionality in 2023: Not only can you now restrict access to certain areas of a repository, you can now restrict what actions individuals can take while working in Grooper! |
About
There may be times where you do not want everyone to have full access to your Grooper repository. After putting in hours of work into customizing your repository design for your company needs, you do not necessarily want someone without training being able to edit your work.
You may have some employees that design the repository and you may have others that simply review the extracted data. Each employee that works with Grooper may have different needs and require different restrictions. With permission sets you can customize who has access to which part of the repository you are working on.
You can also restrict what actions an individual can take while working in Grooper. If you want to avoid someone accidentally deleting a batch or clicking cut instead of copy, you can restrict those actions.
Adding Permission Sets
There are two parts to configuring permission sets: granting/restricting page access and granting/restricting permissions.
Page Access
The first part of configuring permission sets is configuring what groups can have access to which pages in Grooper. By default, everyone has access to every page in your repository. For example, if you would like users to only have access to the "Batches" and "Tasks" pages, we can do that here.
|
|
|
|
|
|
|
|
|
|
|
|
|
Now that we have restricted the pages we wish the "Users" group to have access to, take a look at the next tab to learn how to restrict what "Users" can do in those pages.
Permissions
|
|
|
|
|
|
|
|
|
|
|
|
|













