Why app-scoped workspaces matter
"Our Sales team and Support team share one CRM. But neither should have to dig through the other team's menus every day, just to find their own work."
One shared platform doesn't have to mean one cluttered menu for everyone. Each team can get a workspace that feels like it was built just for them.
Anatomy of an App
Think of an App like a different desk for a different job. Sales has one desk, Support has another โ but both desks sit in the same building, which is your CRM.
An App is a named group of Tabs. A Tab is a button in the top menu that takes you somewhere. It can open an object โ like all your Contacts or all your Cases โ at a web address such as /records/{objectApiName}. Or it can open a built-in page, like Reports or the Dashboard.
| Concept | Detail |
|---|---|
| Tab type: OBJECT | Opens one specific object โ for example, every Contact or every Case |
| Tab type: STANDARD | Opens a built-in page, like Reports, Dashboard, or Marketing Studio |
| App visibility | Controlled by Profile โ App Access. A Profile is a set of permissions every user has. If a Profile isn't granted the app, that app stays hidden from everyone with that Profile |
| Shared tabs | The same Tab can appear in more than one App at once โ e.g. "Reports" can show up in both the Sales app and the Support app |