Regulated industries

For finance, healthcare and the public sector

What a review team in a regulated organization usually asks first, answered with what the workspace does today and a link to the guide that shows it.

A person decides the consequential steps

An action that matters waits for a person: it is sent to the right approver, escalates to a backup when nobody answers, and expires rather than going ahead on its own. Your team's boundary rules are checked before every action, and an action a rule forbids is refused. See Approvals and boundary rules.

Some things a coworker never does by itself, whatever the rules say: a password or verification code field and a pay or checkout button are always handed to a person. See Saved logins and private sign-in.

Every action on the record

The audit trail lists every action a Bot took and every one the rules refused, with secrets masked. Entries are only ever added and each is chained to the one before it, so a changed or removed entry shows. It can be exported, and the evidence pack bundles the trail, the boundary rules and an access review for an auditor. See Audit trail and compliance exports.

An administrator chooses how long the trail is kept, and a legal hold keeps what it covers until the hold is released.

Personal data work, in one place

In the admin console, Compliance overview brings together legal holds, privacy requests with their due dates, recorded personal data breaches with their reporting clocks, people who were removed but still hold access, and the evidence of the last checks. It helps you keep track; it is not a certification and not legal advice.

Privacy programme keeps a record of processing drafted from how each Bot is set up: its purpose, its data sources and the services it sends to. Members' own controls are in Privacy controls for members.

Where data is kept and who receives it

The privacy notice lists what is stored, where backups go and every kind of service that receives data. In the workspace, the data residency report under Compliance shows where each kind of data is stored, read from the deployment's own settings, and says unknown rather than guessing.

Stored credentials are encrypted before they are written, and once a permanent encryption key is set, every database backup is sealed before it leaves the workspace. See Encryption keys.

Who can get in, and where coworkers can reach

What stays with your organization

Whether a setup meets a particular law, regulation or supervisor's guideline is for your organization to decide. The workspace gives you the controls and the records; your compliance team decides how to use them.

To talk it through, write to us on the contact page and choose Security.