2023:Permission Sets: Difference between revisions
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
In this article we will show you how to add and update '''''permission sets''''' to access different areas of a repository in 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. | ||
{|cellpadding=10 cellspacing=5 style="margin:12px" | |||
|- | |||
|style="font-size:200%; background-color:#662d91; color:white; width:28px; text-align:center"|'''‼''' | |||
|style="border: 4px solid #662d91"| | |||
'''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== | ==About== | ||
| Line 17: | Line 24: | ||
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 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==== | ====Adding Permission Sets==== | ||
| Line 88: | Line 97: | ||
|- | |- | ||
|valign=top| | |valign=top| | ||
#<li value=20> In this example, we are going to prevent anyone with the User permission set from deleting batches. Scroll through the | #<li value=20> In this example, we are going to prevent anyone with the User permission set from deleting batches. Scroll through the '''''Command States''''' until you find the "Delete" command and uncheck the box to the right of the command. | ||
# Click "OK" to save your work and close the window. | # Click "OK" to save your work and close the window. | ||
| | | | ||
Revision as of 09:15, 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|













