Skip to content

The Compliance officer role Enterprise

Why it exists. Compliance and data protection people need to run the rules and produce the evidence themselves, without being organisation admins who could also change keys, providers or budgets. The Compliance officer role gives them exactly that. What Enterprise includes depends on the features your licence includes.

An organisation admin gives the role on Who › Roles & access, or on a person's Teams & roles tab (Make Compliance officer). It covers the whole organisation.

What a Compliance officer can do

Area Read Change
Policies, recipes, guardrails, findings, exceptions Yes Compliance policies and their parts
Regulations and the pack library Yes Follow and stop following regulations; copy, make, import and export packs
Approved models (Approved for use) Yes Add and remove, without being given the permission
Guardrail overrides Yes Approve a group admin's request, without being given the permission
Risk levels on agents and applications Yes Set and change them
Retention & legal hold Yes Periods, regulations, legal hold. Deciding a clash is an organisation admin's
Evidence Yes Verify now; ask for the auditor report and evidence pack. Switching tamper evidence and confirming the gateway's key are an organisation admin's
Incidents Yes Record, report and close. Deleting is an organisation admin's
Access reviews, data subject requests Yes Start, decide and close reviews; make requests
Audit log The whole log Export it
Request logs Every call — (exporting calls is for admins)
Dashboard The Compliance view and the impact report —

What they can't do

  • Change others' keys, models, providers, prices, budgets, routing or access.
  • See what a call cost, when it's someone else's call.
  • Read what calls sent and got back, unless they're also given Content reader.
  • Decide on their own access in an access review.

They hold their own key as a member of a team, like anyone else.

On Community

There's no Compliance officer role. An organisation admin does this work: following regulations, retention and legal hold, risk levels, access reviews and data subject requests are all in Community. Two permissions an organisation admin can give, including to themselves, cover the rest: Manage approved destinations and Approve guardrail overrides.