Who uses it
The backoffice is used by Twine staff, vendor customers, and in some cases end customers. Everyone sees the same interface, scoped by the permissions granted through their role. In practice:- Twine staff use the backoffice to set up and manage Organizations and System Integrations on behalf of customers.
- Vendor customers use it to configure property mappings, domain mappings, and templates for the integrations they manage.
- End customers may have access to view their data, check job status, or adjust notification settings.
Access
Authentication is via Google or Microsoft OAuth. There is no self-service registration - Twine creates the Organization, after which a local Organization admin can invite additional users.What’s in this section
The pages in this section walk through how to perform specific tasks in the backoffice. For the underlying concepts, see the Platform section.System Integrations
Settings, authentication, and admin actions for a System Integration.
Domain Mappings
Creating and configuring domain mappings, sync triggers, and time-code mappings.
Entity Matcher
Establishing the initial mapping between local and remote entities.
Anomalies
Viewing and clearing detected data issues.
Jobs
Inspecting sync and replication job runs.
System Data
Browsing entities stored by Twine.
Templates
Reusing property mapping configurations across customers.
Notifications
Configuring email digests for anomalies and data events.