Org structure, app licenses and packages

Multi-tenant architecture, the license gate, and how apps are enabled or disabled per org.

Multi-tenant architecture

In Ohana360 every company works in its own org. Orgs are fully isolated from each other: users, records, settings, automations and files belong to the org. A user of one org can never see another org's data.

App licenses (the license gate)

Which apps are active in your org determines what you can see:

• Only the tabs, objects, data and features of active apps are visible.
• The data of a disabled app is never deleted; it goes dormant. When the app is re-enabled, all data comes back exactly as it was.
• Object pickers in reports, global search, flows and import screens are filtered by license too.

The base package (Platform360) is always on in every org: Accounts, Contacts, Tasks, custom objects and reporting live there.

Enabling and disabling apps

1. Open the Marketplace from the app launcher.
2. Click Enable on the card of the app you want.
3. The app is added to the app launcher immediately and its tabs become visible.

Roles: Administrator and Super Admin

• Administrator: The person who created the org and anyone they authorize. Has access to Setup screens, user management and all settings.
• Super Admin (Ohana360 HQ): The platform operator. Manages orgs and may enter them for support purposes, always audited. The "Ohana360 Service" setting lets you manage this access per org (inside Setup).