Keep the source record, responsible people and next operating decision connected in your own workspace.
Maintain workspace identity, membership and permitted responsibilities without changing another workspace.
Workspace settings describe the organisation using Spends Control. Personal details belong to an individual account. Updating a company name or logo should not be confused with transferring ownership or changing another member’s password. Keep the brand identity accurate so colleagues recognise the workspace they have entered.
Confirm which identity the setting applies to.
Invite colleagues who need to participate in the operating workflow. Check the intended role and workspace seat capacity before issuing an invitation. An invitation is a request to join, rather than evidence that a colleague has already accepted. Remove obsolete invitations through the authorised membership controls when responsibilities change.
Check the invite recipient and intended role.
The Super Admin owns the workspace. Delegated administrators, editors, viewers and specialised roles receive access according to the granted scope. Custom roles can distinguish View, Edit, Create and Delete permissions by section. A visible button does not replace backend authorisation, and a record assignment does not justify granting access to unrelated company data.
Grant the permissions required for the actual work.
Section access and individual record assignments can describe different responsibilities. Department-scoped colleagues should work within the scope granted to them. Before transferring a service to another person, check whether that colleague needs record visibility, editing rights or only a specific task. Keep approval authority separate from day-to-day administration.
Review the assignment against the member’s scope.
Profile settings cover personal details, password changes and two-step verification. Notification preferences control how supported alerts reach the user. Protected account changes require the appropriate authentication flow; a general workspace edit should not bypass it. Review account access when a colleague leaves the organisation.
Use the relevant account security control.
Workspace settings describe the organisation using Spends Control. Personal details belong to an individual account. Updating a company name or logo should not be confused with transferring ownership or changing another member’s password. Keep the brand identity accurate so colleagues recognise the workspace they have entered. Confirm which identity the setting applies to.
Invite colleagues who need to participate in the operating workflow. Check the intended role and workspace seat capacity before issuing an invitation. An invitation is a request to join, rather than evidence that a colleague has already accepted. Remove obsolete invitations through the authorised membership controls when responsibilities change. Check the invite recipient and intended role.
The Super Admin owns the workspace. Delegated administrators, editors, viewers and specialised roles receive access according to the granted scope. Custom roles can distinguish View, Edit, Create and Delete permissions by section. A visible button does not replace backend authorisation, and a record assignment does not justify granting access to unrelated company data. Grant the permissions required for the actual work.
Section access and individual record assignments can describe different responsibilities. Department-scoped colleagues should work within the scope granted to them. Before transferring a service to another person, check whether that colleague needs record visibility, editing rights or only a specific task. Keep approval authority separate from day-to-day administration. Review the assignment against the member’s scope.
Profile settings cover personal details, password changes and two-step verification. Notification preferences control how supported alerts reach the user. Protected account changes require the appropriate authentication flow; a general workspace edit should not bypass it. Review account access when a colleague leaves the organisation. Use the relevant account security control.