Customization and integrations

Guidance for source changes, provider integrations and building the mobile app.

Use this page with AI Open in Claude Open in ChatGPT View as Markdown

Start with company details, localization, roles, approval workflows and module settings. See the settings overview and roles and permissions.

For source changes, put your features in your own module so Core updates never overwrite them (see Building your own module); keep it in version control and re-test after updates. Keep business rules in the backend and use the shared API across clients. Rebuild assets after changing frontend source/public configuration. Never put secrets in VITE_* variables.

Provider integrations require customer accounts, permissions and their own costs. Enable only configured and tested integrations. Distribute examples rather than customer credentials.

The mobile source contains one HR application in apps/hr/, including chat, calls, email/calendar, feed, presence and contacts when enabled. Preserve its HR application identity, signing and Firebase registration when updating an existing HR installation. The former Communications application is retired; users sign in to HR. Grant HR app access explicitly to roles that previously only had Communications access. Existing Communications sessions cannot be reused. Server conversation history remains available, but local drafts and cached files from the old app are not automatically transferred. Save any unsent work before uninstalling that app.

Source builds need the application, composition package, core package and selected optional feature packages. Follow apps/README.md to export a full, core-only or selected-feature build. Calls requires Chat. Removing a package from a build does not delete its server data. Server modules and user permissions still control access; compiling a feature does not grant it to users.

Organizations enable backend modules and configure Microsoft 365, calling and push providers. Keep one backend and user directory. Add-ons are bought and installed from Settings → Modules (see Installing and managing add-ons). Signing, store distribution and physical-device acceptance remain separate tasks; validate background push and calling with your actual providers.

For mobile sign-in legal links, set OPEN_CORE_HR_TERMS_URL and OPEN_CORE_HR_PRIVACY_URL to your organization-owned HTTPS documents in the app's local Dart configuration. Empty or invalid values omit the links; the app does not show placeholder agreement buttons.