LaneyGuide
Preparation

Set organization and data permissions

Select the working organization first.

How-toVerified Oct 12, 2026Owner Laney Product

After this taskThe permitted operation completes; the denied operation causes no write.

Starting conditions and inputs

Have an authorized administrator and a separate staff test account.

Values for this task

entry_url, organization_id, member_ids, role_ids, allowed_operation, denied_operation, allowed_operation_url, denied_operation_url

Command sequence

open "$entry_url" && snapshot -i

click "$member_row" && snapshot -i

get text body

click "$role_picker" && snapshot -i

click "$role_option" && snapshot -i

get text body

# Outside browser: Prepare a separate session signed in as the test member.

open "$allowed_operation_url" && snapshot -i

get text body

open "$denied_operation_url" && snapshot -i

get text body
Ref targets and expected results
#Command / refTarget and verification
1click $member_rowMember record to change
2get textCompare member and organization IDs.
3click $role_pickerMember role picker
4click $role_optionPermitted role option
5get textRead stored role and organization scope.
6Outside browserPrepare a separate session signed in as the test member.
7openPage for an allowed member operation
8get textRead the permitted operation result.
9openPage for a denied member operation
10get textRead the denial and compare the source record for unintended writes.

Check the result

The permitted operation completes; the denied operation causes no write.

Resuming after interruption

Read the same IDs again. Preserve correct settings and update only differences.

Choose the organization

Select the working organization first. Confirm which organization owns each new record. For example, give branch employees access to branch reservations without access to every customer at headquarters.

Assign staff roles

Open Members and check the organization, role, and active status. Use Roles to set which records the employee can read and change. Sign in as that employee to check access. A hidden menu alone does not prove that data access is denied.

Set the automation actor

The workflow owner determines its execution permissions. Review workflows when their owner leaves or changes role. A prompt cannot grant administrator permissions. Assign the required read and write access through the role.

Check allowed and denied actions

Use a test record to check an allowed read and edit. Then check that another organization’s records and unauthorized actions are denied. Record the account, organization, action, and result. Reduce excess permissions.

On this page