Permissioned surfaces
Navigation, route handlers, and read models hide or scope data based on explicit permissions.
RBAC and logs
Permissions, audit events, records, and logs for operational review.
Role-aware admin surfaces, organization-scoped RLS, audit events, work-item history, and integration ledgers help teams understand what changed.
Launch posture
Trust and readiness
Permissions, audit events, RLS, owner-confidence snapshots, and logs support controlled launch but are not a compliance certification.
Asset slot
Admin role/access controls and audit/report summary
Capture access modal, reports, and audit summary after final owner/admin examples are ready.
What is ready now
These points describe shipped product behavior or explicitly scoped setup readiness. Final screenshots and recordings will be captured from the product after demo data is frozen.
Named admin permissions and role assignments
Organization-scoped row level security
Audit events for sensitive admin, billing account, export, and deletion actions
No certification claim
These controls support launch readiness but are not a SOC 2, ISO, HIPAA, or penetration-test attestation.
Included scope
- Named admin permissions
- Organization-scoped RLS
- Audit events
- Operational logs
- Owner-confidence report snapshots
- Permission matrix
Not included
- SOC 2 attestation
- ISO 27001 certification
- Penetration-test attestation
- Compliance guarantee
Asset source tracking
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
- Route
- /rbac-auditing-records-logs
- Surface
- Admin role/access controls and audit/report summary
- Organization
- Approved demo organization after final seed reset
- Viewport
- Desktop 1440x1024 and mobile 390x844
- Data set
- Synthetic approved demo data only
- Refresh date
- Pending final product capture
- Refresh trigger
- Refresh after material UI, legal copy, seed data, data model, or route changes
Buyer FAQ
These answers keep trial, support, export, provider, AI, mobile, and trust expectations consistent across the public site.
Can I start without a sales call?
The current path supports controlled trial activation. No-card demo tenants remain support-approved so capacity, provider setup, sensitive uploads, and data-retention expectations stay bounded.
What happens if we cancel?
Paid access normally ends at the end of the billing period, then the workspace enters a 30-day export/reactivation window unless a verified deletion request is completed earlier.
Does Yrka process payroll or file taxes?
No. Yrka supports timekeeping, payroll-prep exports, review, and provider handoff. Customers remain responsible for payroll processing, tax filing, legal, HR, and compliance decisions.
What mobile support is included?
Launch mobile support is responsive web/PWA-oriented. Employees get scoped offline read context and supported queued writes with visible sync states; native app-store apps and broad offline admin operation are not part of launch scope.