Flowis offers a unique way of setting up permissions for as many different groups of employees as needed. Its complexity allows you to truly set up Flowis and the information in it with precision, making sure everybody can see, access, edit, and delete only the information they are allowed to.
You can set up permissions for Transactions, Definitions, and the Administration section (items in the left menu).
Permissions for the Administration section
- Basic – Users can see only the things allowed in other Permissions (see the next part of this article) or Custom Tabs
- Admin – Users can see every section in the left menu, but can not set up Ruby Evals and Passwords. Admin should be only someone who can set up every part of Flowis, who was trained to use Flowis or went through our Flowis University
- Owner – Users can see every section in the left menu and can set up Passwords and System Accesses (SMTP, Office365, External Applications, etc.), but they can not set up Ruby Evals
- Vendor – Users can see every section and set up everything, including Ruby Evals and Code Snippets – only SoftPoint employees should have this role
Permissions for Transactions and Definitions
The setup of permissions for Transactions and Definitions is very complex and offers great flexibility. You can find the following items in the left menu:
- Create permissions – to create a new Transaction or new record in a Definition
- Access permission – to see that the Transaction or the record in a Definition exists; to see it in the list
- Show permissions – what is shown after opening a specific Transaction or record in a Definition
- Edit permissions – to edit data on a Transaction or record in a Definition
- Filter permission – which fields are available in the filter on the top of the screen when you are in the list of Transactions or a Definition
- Comment permissions – to add a comment to a Transaction
- Duplicate permissions – to duplicate a Transaction
- OCR validation permissions – to set up the optical character recognition for Transactions
Each of these permissions is further described in a separate article.