Review first
Import Center owns hands-on intake. Integrations owns movement, health, connection state, source status, and delivery history.
Integrations
Connection health, imports, exports, sources, and webhooks without hidden automation.
Review external connection metadata, sync jobs, webhook ledgers, notification delivery, source readiness, and provider setup status.
Launch posture
Provider-gated substrate
Connection health, ledgers, reviewed file/profile paths, configured calendar/source OAuth sync, notification pipes, SSO policy gates, payroll handoff evidence, source readiness, and provider setup status are visible while unsupported provider APIs remain gated.
Asset slot
Integrations overview with provider health cards
Capture after final provider-readiness demo rows are refreshed. Do not imply live OAuth unless configured.
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.
Provider connection registry and sync/webhook ledgers
Reviewed calendar/source sync into Schedule import review and Resources source review
Notification delivery history for email, Slack webhook, Slack app OAuth, SMS, and Web Push/PWA pipes
Readiness messaging for integrations before unsupported provider setup
Setup is explicit
Live provider setup depends on customer authorization, provider apps, credentials, and supported adapters.
Included scope
- Connection registry
- Sync job ledgers
- Webhook ledgers
- Notification delivery history
- Reviewed Google/Microsoft/Apple ICS calendar import profiles
- Live Google and Microsoft Calendar sync into Schedule import review when provider OAuth credentials, customer authorization, and selected calendar/date-window setup are configured
- Reviewed Notion and Google Drive source export profiles
- Live Google Drive, SharePoint/OneDrive, and Notion source sync when provider OAuth credentials, customer authorization, and selected source ids are configured
- Server-configured email digest, Slack webhook, Slack app OAuth, Twilio SMS, and Web Push/PWA notification pipes
- Google and Microsoft sign-in policy diagnostics with allowed-domain and pending-access review gates
- Provider-gated payroll bridge setup-review and time-export handoff evidence without payroll submission
- Source readiness status
- Provider-gated setup state
Not included
- Live OAuth unless configured
- Guaranteed third-party provider uptime
- Provider contract management
- Custom provider apps by default
Asset source tracking
Product imagery is published only after the capture source, demo organization, viewport, data set, and refresh trigger are recorded.
- Route
- /integrations
- Surface
- Integrations overview with provider health cards
- 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.
Are provider integrations live by default?
No. Live provider use depends on customer authorization, provider credentials, provider app approval, adapter support, and environment configuration.
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.