Contribute an App profile tab
Declare an App-owned profile screen and its admission permission.
Contribute an App profile tab
An App contributes a tab and screen to My Profile with one ProfileTabDescriptor. Adopt the matching PHP SDK, Core and App runtime before submitting the App. Core owns Overview; Apps must declare their business tabs explicitly. Legacy slot-only declarations no longer create tabs in this host revision. Migrate installed Apps before adopting this revision.
use Nexia\AppDescriptors\AppDescriptorSet;
use Nexia\AppDescriptors\Contracts\AppDescriptorContribution;
use Nexia\AppDescriptors\ProfileTabDescriptor;
final class WorkshopProfileTabs implements AppDescriptorContribution
{
public static function appDescriptors(): AppDescriptorSet
{
return AppDescriptorSet::of(new ProfileTabDescriptor(
key: 'workshop.records',
labelKey: 'workshop.profile.records',
component: 'WorkshopProfileRecords',
permission: 'workshop.record.read',
));
}
}The key and permission must belong to the App, and the permission must also be declared in its catalog. Supply translations for labelKey and add the frontend component to the existing overrides registration:
overrides: {
WorkshopProfileRecords: () => import('./profile/WorkshopProfileRecords'),
},The component receives ProfileSlotPropsV2 from @nexia/sdk, including the selected work context. Do not infer an employee when workContext is null. The App owns the screen and its actions, and must authorize each read and write in its API. Tab admission does not replace data authorization.
The host checks App installation and operational status and the user's Self permission. The tab URL is /me/workshop.records. No Dashboard widget declaration or user layout editing is needed. To place a widget in another surface, see the host slot guide.
See the PHP SDK descriptor source. Verify that the tab is hidden for a user without permission and when the App is disabled, and that data is reauthorized after work-context changes and permission revocation.
Compose existing widgets
PHP SDK 0.10.28 introduced grouped tabs and legacy aliases. Use a published package and lock compatible with the target Core; source checkout tests do not prove that a running runtime adopted it.
new ProfileTabDescriptor(
key: 'workshop.records',
labelKey: 'workshop.profile.records',
sort: 20,
widgetKeys: ['workshop.self.summary', 'workshop.self.requests'],
legacyTabIds: ['records'],
);Use either component plus permission, or widgetKeys, never both. Grouped
widgets must be declared by the same App in supported personal profile slots.
Each child retains its permission, order and work context; an empty authorized
group is hidden. Core Overview now shows the current user's identity, contact
details and effective roles. It does not compose App summaries or action cards,
and Profile does not offer dashboard placement controls.
The former Core business tabs and My Organization placement are removed.
profile.team.overview is no longer composed here; use the App's standalone
organization workspace. Existing dashboard destinations remain independent.
legacyTabIds maps an old address to its App tab while retaining query parameters.
Do not claim overview; unknown or conflicting aliases return to Overview.
Before applying this compatibility change, migrate installed slot-only Apps to explicit tab descriptors, verify permissions and disabled Apps, work-context changes, old links and action return paths. Coordinate the host release under the pre-1.0 breaking-change version policy; no operational migration is claimed by this source change.