| AWRA OpsHub

 Search
Advanced Certificate on pass

Security, Compliance, and Recovery

Protect the system through access control, device trust, document evidence, audit logs, trash recovery, and legal holds.

3 lessons 45 min 5-question assessment 80% to pass
Take the assessment

What you’ll learn

  • Connect roles, MFA, devices, and sessions into one access model
  • Use documents and evidence packs for compliance proof
  • Recover safely using trash, impact previews, and legal holds
  • Investigate incidents from logs and source records

Course content

3 lessons · 45 min of reading
01
Lesson 1 of 3 Reading 14 min

Access is a living control

Security is not only login. In AWRA, access is shaped by roles, permissions, MFA, device trust, session control, plan entitlements, and sensitive action throttles.

A secure tenant is reviewed regularly. People change roles, devices get lost, vendors leave, and support access must be controlled. The access model must move with the business.

Access control layers

Layer Controls Review question
Identity Login, password reset, MFA Is this person still who they claim to be?
Role Permissions and least privilege Can they do only their job?
Device Trust, lock, unlock, revoke Is this device still safe?
Session Terminate user or device sessions Should current access continue?
Support Impersonation with audit Was support access justified and recorded?
02
Lesson 2 of 3 Lab 15 min

Evidence that survives an audit

Compliance proof is built while people work, not after the auditor arrives. Signed downloads, secure attachments, document vault files, audit logs, and evidence packs all help answer what happened and who approved it.

The goal is not more paperwork. The goal is enough structured evidence that a reviewer can trust the record without chasing private chats and scattered files.

Evidence path

1

Action happens

A user changes access, approves spend, records payment, moves stock, or uploads a file.

2

System records context

Actor, timestamp, tenant, module, record, attachment, and status.

3

Evidence is packaged

Document vault and evidence packs gather proof for review.

4

Reviewer follows trail

Audit logs and source links answer the who, what, when, and why.

03
Lesson 3 of 3 Practice 16 min

Recovery, deletion, and legal holds

Deletion in an operations platform is sensitive because records often have downstream meaning. Trash recovery, impact previews, force delete approvals, legal holds, and purge reports turn deletion into a governed workflow.

The safest recovery routine asks three questions: what is being restored or removed, what depends on it, and what evidence proves the decision was authorized.

Recovery safety checks

Open impact preview before destructive action
Use legal hold when a record is under dispute or audit
Require approval for force delete when policy demands it
Restore source records before dependent records when possible
Review purge reports for what was permanently removed
Keep notes clear enough for a future reviewer

Finished the material?

Take the 5-question assessment and earn your certificate — 80% to pass.

Take the assessment

More in this path

Workflow Builder Basics

Open course

Approval Workflows

Open course

Security & Data Protection

Open course

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center