Expert suites

Expert suites combine capabilities and configuration for a particular kind of work. Administrators maintain market sources, resource review, and member access. Availability: Expert suites is not displayed in the current international console's AI Assets menu. Use the steps below only when Expert suites is enabled for your deployment and available in your console.

​

Configure suite markets

1. Open AI Assets → Expert suites → Market management where available.
2. Enable the official and enterprise markets as needed.
3. Configure the enterprise market as dedicated or private. Dedicated suites are maintained here; private markets require a full page URL and allowed origin.
4. Save and check client access. Private-market content comes from the enterprise's own system. The console list and upload approvals require dedicated-market mode.

​

Upload and organize enterprise suites

1. In an enabled dedicated market, open the list and add a suite.
2. Enter its name, unique identifier, version, category, and description. Explain the work it supports.
3. Optionally attach an icon and ZIP. Icons must be square PNG, JPEG, or WebP files of up to 2 MB; suite ZIPs are limited to 50 MB.
4. Place packaged skills under skills/<skill-name>/SKILL.md. Filenames are case-sensitive.
5. Save and publish, check the version and enabled state, then configure publication policies.

The icon and package are optional. Existing official suites can be added from the official market.

​

Review member submissions

Configure permission to add suites themselves separately from permission to upload suites to the dedicated market. Review submitted contents in upload approvals. Choose a category when approving, or provide specific revision guidance when rejecting. Check that intended members can use the suite's referenced services and resources. Publishing it does not grant external business-system permissions.

​

Publish to a team

1. Add a publication policy group.
2. Choose allowlist or blocklist, member scope, suite scope, and client targets.
3. For automatic installation, use an allowlist with specific resources. All resources cannot be combined with automatic installation; blocklists do not support it.
4. Save, enable, and have members inside and outside the team check client visibility.
5. Have a target member run a representative task and verify dependent resources.

Blocklists take precedence. The default allow policy is always enabled, but its resource scope can be edited. Check affected teams before disabling a suite. After deletion, verify that related policy references have been removed. Return to: AI Assets overview