Displays a grid view of each state, its actions, and all database roles where you can specify which roles can perform the selected workflow action.
Assigning permissions to roles rather than directly to users is the preferred method for setting up database security. It is far easier to maintain and makes it easier to save your solution as a template. When you save a solution as a template, you do not want to have specific user security set up, because these users can change or have different permissions in various solutions.
By default, all database roles are granted permissions to perform all workflow actions. To grant permissions to perform specific actions to specific roles, select those roles that can perform the action, and clear the box next to roles that should not have permissions to perform the action. You can also select a range of cells, rows, or columns in the grid and right-click to open the shortcut menu where you can grant or deny permissions for the entire selection.
| For information about | See |
| Adding a workflow process to your solution | Building a Workflow Process |
| Assigning permissions to workflow actions | Controlling Permissions for an Action |
| Working with the workflow states | Adding and Modifying States in a Workflow |
| Working with actions associated with workflow states | Adding and Modifying Actions for States |
| Adding script to workflow actions | Scripting Workflow Actions |
| Adding database roles to your team solution | Creating Database Roles |
| Defining a table hierarchy for your solution database | Setting up a Table Hierarchy |