Activating and managing Apps

Find an App

Open Settings → Apps to review optional Practize features and integrations. Apps are grouped by purpose, such as Online Booking, services, payments, accounting, security, or practice administration. You can also open the settings page for an active App from the Settings overview when that shortcut is available.

An App can have several different states:

• available to activate;
• active but still requiring setup;
• active and ready to use;
• unavailable because of permissions, country, subscription, compatibility, or rollout requirements; or
• scheduled to change with the practice subscription.

Seeing an App card or catalog price does not prove that the App is active, configured, or available for purchase. The Apps and Subscription screens for the signed-in practice are authoritative.

Activate and configure an App

1. Open the App from Settings → Apps.
2. Read the description and any availability message.
3. Choose the activation or connection action when it is offered.
4. Complete the App-specific setup. An integration may require authorization with its provider; other Apps require calendars, services, templates, or business settings.
5. Return to the App settings page and confirm its displayed status.

Only a practice owner or a user with the required App-administration permission can activate or deactivate Apps. Activating an App does not bypass its normal record permissions.

Deactivate an App safely

Before deactivation, review whether the App has active bookings, payment flows, memberships, messages, accounting connections, automations, or other dependent records. Follow the confirmation shown by Practize. Deactivation can hide actions or stop future processing, but it does not necessarily cancel an external provider agreement or reverse a completed provider transaction.

Troubleshooting

• If activation is missing, check owner permissions and Settings → Subscription.
• If setup is incomplete, reopen the App and complete every required step.
• If two Apps are incompatible, follow the compatibility message instead of repeatedly toggling them.
• If a provider connection fails, verify its status from the App screen without sharing credentials in chat.

Never put OAuth codes, API keys, access tokens, webhook secrets, payment credentials, client records, or provider response payloads into a product-help question.