Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Security & Compliance
Security controls for the work your teams cannot afford to lose.
AWRA OpsHub protects organization data, permissions, MFA, sessions, devices, encryption boundaries, and audit history across inventory, procurement, sales, accounting, mobile, and vendor workflows.
Organization Isolation Scoped
Operational records stay bound to the correct organization context.
Access Control Permissioned
Roles and module permissions govern user actions.
Sessions Managed
Device trust, force logout, and inactivity controls apply in the browser and the mobile app alike.
Audit Trail Reviewable
Sensitive operations keep accountability context.
Active control areas
MFA Role Permissions Plan Governance Audit Logs Mobile Trust
Security control layers
Protection built into daily operations, not bolted on later.
AWRA security is designed around the work people actually do: moving stock, approving purchases, issuing invoices, managing vendors, syncing mobile devices, and reviewing finance records.
Org Isolation
Organization-scoped records and access boundaries help prevent cross-organization data exposure.
Identity Controls
MFA, verified accounts, strong passwords, trusted devices, and session controls protect entry points.
Permission Model
Role permissions and plan controls define which screens, actions, and modules users can access.
Audit History
Critical operational changes preserve who, when, what, and why for review and accountability.
Trust operations
Security reviews need evidence, not slogans.
When your team or customer asks how access, mobile sync, permissions, and sensitive actions are controlled, AWRA should make the answer clear and reviewable.
01
Authenticate The User
Verified identity, MFA policies, password requirements, and session checks protect access.
02
Authorize The Action
Roles, permissions, plans, and organization policies decide what the user can actually do.
03
Record The Event
Sensitive actions, approvals, impersonation, device activity, and operational changes keep review context.
04
Monitor Exceptions
Security and admin views surface devices, sessions, impersonation, scheduler, push, and plan access context.
05
Respond And Recover
Admins can revoke trust, terminate sessions, review activity, and coordinate support when needed.
Mobile and device trust
Offline work still needs controlled access.
AWRA mobile offline workflows depend on trusted-device rules, one-day offline unlock windows, sync queues, GPS proof where required, and server-side validation when actions reconnect.
Your workspace security policy applies in the app as it does in the browser — at sign-in and on every request: sign-in only through your identity provider when SSO is required, password expiry, the IP allowlist, device approval, the idle timeout and the absolute session lifetime. A biometric unlock cannot stretch the absolute limit.
Trusted Session
Offline unlock is limited to devices that previously signed in and were trusted.
Sync Authority
Queued mobile actions still pass server policy and permission checks when synced.
GPS Evidence
Asset movements can preserve coordinates, accuracy, source, and timestamp.
Device Approval
With device approval on, a new phone is identified by its app install and held until an administrator approves it.
Same Network Rules
An IP allowlist that restricts the browser restricts the app too, so the office-network rule has no side door.
Admin Response
Device trust and sessions can be reviewed and revoked when needed.
Smart Recommendations
After access is controlled, reviewers look for proof.
Security pages should help teams move from feature posture to review-ready evidence. These next paths connect mobile trust, architecture controls, compliance status, legal terms, and governance depth.
Security review sequence
From entry control to incident-ready evidence.
01
Protect entry points
Validate MFA, trusted sessions, mobile unlock rules, and device revocation paths.
02
Constrain permissions
Check roles, organization boundaries, plan gates, and sensitive action access.
03
Preserve evidence
Confirm audit trails for approvals, impersonation, device activity, and operational changes.
04
Prepare response
Line up review screens, support paths, legal docs, and uptime expectations before escalation.
Device policy
Device Trust
Review how trusted devices, mobile access, sessions, biometric revocation, and remote logout strengthen field operations.
Architecture proof
Security Whitepaper
Open the deeper control narrative for encryption, identity, isolation, secure delivery, and operational hardening.
Control posture
Compliance Status
See which controls are implemented, where evidence lives, and how ownership is framed for reviews.
Security stakeholders also open
Trust resources, legal safeguards, uptime terms, and governance controls.
Administrator controls
The settings a security reviewer asks to see switched on.
Each of these is a page under Settings, used by your own administrators. Every change to them is written to the audit log.
Audit log streaming
Every new audit entry is pushed to Splunk, Datadog or your own HTTPS endpoint within about a minute, carrying its hash-chain values so your SIEM can tell if anything was dropped or altered.
AI & data controls
One switch stops your organization sending anything to a third-party AI provider. The page lists which providers are in use and logs each call by provider and purpose, never its content.
Sandbox workspace
A separate copy of your roles, permissions, approval rules and procurement settings, with none of your records, to try a change in first. It sends no email.
Out-of-office cover
An approver hands their approval steps to a named colleague between two dates. The delegate is told, and every decision records on whose behalf it was made.
Security review areas
The controls customers usually ask about.
Security reviews should cover how users enter, what they can access, how actions are traced, and what happens when something needs investigation.
Data Protection
TLS in transit, protected storage practices, backups, and controlled access to operational data.
Access Governance
Roles, permission groups, plan access, organization overrides, and admin review screens.
Auditability
Activity, approvals, impersonation, sensitive changes, and operational records should remain reviewable.
Operational Resilience
Backups, scheduler health, sync visibility, and support workflows help keep operations accountable. A timed restore drill can restore the newest database backup into a separate database and record how long recovery took and how old the backup was.
Explore AWRA
Security connects to every workflow.
See how core modules enforce access control, approvals, and auditability.
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.