Evaluating Permissions in a Shared Software Product

List the kinds of user access your proposed use requires. Describe the task each user needs to complete before asking how a product's permission settings support it.

Test with synthetic records

Create a demonstration plan with a record a user should be able to see and another they should not. Ask the demonstrator to show both permitted and refused actions. Do not use real customer or employee information to make the test look realistic.

Inspect changes in access

Ask what happens when a user's access is reduced or removed. Check which settings apply to viewing, editing and exporting, rather than treating all access as one switch. Record which behavior you actually observed.

Read the documented scope

Review the permissions described for the product and offer you are considering. A feature list or role label does not establish the behavior of every action.

Use developer documentation to identify STEADYWRK interface requirements. Retain the observed permitted and refused actions with your comparison notes.