...
Authorizations are given to groups. The authorizations of users added/removed to groups are automatically updated.
If no selection is made for any group, it is interpreted as no authorization and in this case the authorization button is unlocked. |
...
Users
Users can come from the LDAP/AD side or be GEODI users.
...
It can also be integrated with the user authentication features of services such as Facebook and Google.
Project-Based Permission
Permissions specific to the project are defined. If no permission is granted to any group, all users will have access to all permissions.
Can View Project: Specifies which groups can view the project.
Can Edit Project: Grants permission to make changes in the project.
Can Index Project: Authority to scan the project from scratch or for changes.
Can Delete Project: Permission to delete the project. If this permission is not granted, the delete button will not be visible.
Can Generate Reports: Allows export reports for the project.
Data Operator: Authority to label and group recognized results recognized by modules like FacePro, TextPro.
Resource-Based Permission
Resource-based authorizations can be set up within the project. If no permission is granted to any group, all users will have access to all permissions.
Can Search: Specifies who can see the relevant resource.
Can Share: Allows sharing from the Twitter account defined in GEODI.
Can View/Download: Grants permission to download and view files in the relevant resource to authorized users.
Can Add Notes: Permission to add notes to files and folders in the relevant resource.
Can Edit Others' Notes: Allows intervention in other users' notes.
Can Add/Feed: Allows uploading files to the relevant resource via the browser.
Expand | ||
---|---|---|
| ||
To view the permissions of a logged-in user and clear the permission cache in GEODI, the following steps can be applied. Api → User Manager Api section.
|