Mitti (formerly SafetyCulture)

Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.

Planned workflows

Planned for Mitti (formerly SafetyCulture):

You text	What would happen in Mitti (formerly SafetyCulture)
“Forklift 2 failed pre-shift, brakes soft (photo)”	Logs the failed inspection and opens a high-priority action
“Tag Forklift 2 out of service”	Updates the asset

These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.

Before you start

Mitti is the renamed SafetyCulture platform. Its developer guide uses api.mitti.com; existing SafetyCulture tokens remain valid. Rebrand guidance.

Developer setup — once

1. Use the Mitti authentication reference and verify the write endpoint for each intended inspection, action or asset workflow.
2. Implement encrypted token storage with a separate connection for each organization. Tokens act as their owning user/service user and do not override item-sharing rules.
3. Prefer a service-user token for a shared, long-running connection; agree with the customer on the access it needs.

Customer setup — repeat for each organization

1. Confirm a Premium or Enterprise plan and a full seat. For service-token creation, the admin also needs platform-management permissions for Organization, Permissions and Users.
2. Open the organization menu → Integrations → API tokens → + Create API token.
3. Name the service user, select an inactivity-expiration period and restrict its permission sets. All permissions are selected by default, so review them before creating the token.
4. Create and securely copy the token. Confirm the service user’s access to the required sites and items.
5. For a personal connection instead, use My Profile → Settings → API tokens → Generate API token and follow the account-password prompt.

These are the two flows in the authentication guide.

Verify write access

Use one test site and asset. Exercise the specific supported action/inspection endpoint, then verify the record, site and assignee in Mitti. Confirm an unshared item is inaccessible. Do not assume an inspection can be edited merely because it can be exported; validate each intended write operation before promising it.

Disconnect and troubleshoot

Revoke the dedicated token in the corresponding API-token management page, remove its stored copy and verify access fails. For missing records, check sharing and site access as well as permissions. For previously working connections, check the selected inactivity expiry before generating replacement credentials. Personal-token revocation.

Who completes the work?

An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.

Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.