Explore Management

https://app.example.com is an example address. Replace it with the actual address of your environment, retaining the route path and query parameters.

1. Configuration Goal

In Explore Management, configure published immutable versions from Resource Hub as discoverable and usable Explore resources, and maintain their display information, order, Role visibility, and version-update mode.

Explore Management configures only distribution information for published resources in Explore. Resource files, user-side access policies, and version content should be completed in 07 Resource Hub first.

2. Configuration Entry

Configuration entry: Resources → Explore Management

app.example.com is an example domain. During actual operation, replace it with the AOS Work access domain for the customer environment. Keep the route path /admin/skillhub/explore unchanged.

3. Pre-configuration Checklist

Before starting, confirm:

1. The current administrator has permission to view the list, create Explore Releases, edit display configuration, adjust ordering, configure Role visibility, and configure the version mode;
2. The target resource has passed structure and security validation in Resource Hub and has at least one published immutable version;
3. The icon, name, description, and display position for the Explore card are confirmed;
4. The Roles that can discover the resource are confirmed;
5. The version-update mode is confirmed: always use the latest version or pin a specific version;
6. If configuring a Connector, confirm that its authorization, connection test, and minimal capability-call path work correctly.

4. Published Resource List

After opening the page, the list shows resources that have been published to Explore. The page provides the following categories and operations:

• All: View all resources currently in Explore;
• Skills: View Skill resources;
• Work: View Work resources;
• Connectors: View Connector resources;
• New: Create an Explore Release from Resource Hub;
• Visible roles: Filter the list by visible Role;
• Search published resources: Search published resources.

The main list fields are:

The list shows only resources already published to Explore. It does not show drafts in Resource Hub that have not been published or versions that have not been added to Explore. Click a resource row to open its detailed configuration.

5. Create an Explore Release

5.1 Select a Published Resource

1. Click New;
2. In Select from Resource Hub, select the target resource;
3. Select only a resource that has been published in Resource Hub and has not yet been added to Explore;
4. Confirm the resource type and target version;
5. Create the Explore Release and open its detailed configuration.

The selection does not include Resource Drafts, unpublished versions, or Git branch content. After an Explore Release is created, the resource name, description, files, and immutable version content in Resource Hub remain managed by Resource Hub.

5.2 Pre-publication Checks

After creation, first check that the resource meets the conditions for user availability:

• The Resource Version has passed common and type-specific validation;
• Explore can display the resource card and details;
• Users can add the resource and complete the required authorization declared by the resource;
• A Connector can create a user Connection and complete Test Connection and at least one minimal capability call;
• Connector reauthorization and unbinding paths work;
• The management display configuration contains no user credentials or plaintext Secrets.

6. Display: Configure Explore Display Information

In the Explore Release details, open the Display tab to configure display information in Explore cards and lists:

These fields affect only display in Explore. They do not modify the Resource Hub resource name, resource description, or version file content.

Save the Explore Release after making changes. To adjust ordering, use the ordering control on the left side of a resource row in the list.

7. Visible Roles: Configure Role Visibility

7.1 Select Visible Roles

In the Visible Roles tab, select one or more Roles allowed to discover the resource:

1. Open Visible Roles;
2. Select one or more user Roles;
3. Save the Role visibility scope;
4. Return to the list and use the Visible roles filter to verify the result.

Multiple Roles use OR matching: a user can discover the resource in Explore as long as they have any selected Role.

7.2 Empty Role Scope

If no Role is selected, the resource is visible to all Roles. Visibility is determined only by the user's current Roles; no department scope is configured. When the user enters Explore, the system recalculates resource visibility from the user's current Roles.

8. Version updates: Configure the Version-update Mode

Click the target row in the resource list, then open the Version updates tab in the right-side details panel. The panel's Version mode provides two radio options and explains that when the current Explore version changes, users who already have the resource are updated by default.

8.1 Always use latest version

Select Always use latest version:

1. Resource Hub publishes a new version of the resource;
2. The Explore Release automatically switches to the latest published version;
3. Users who already have the resource are updated to the new current version.

This mode is suitable when users should continuously use the resource's latest capabilities.

8.2 Specific version

After selecting Specific version, select and save a target version from the resource's published immutable versions. When Resource Hub later publishes a new version, the current Explore Release continues to use the selected version. To upgrade, return to Version updates and select another published version.

This mode is suitable when a new version must be verified before an administrator decides when to switch.

8.3 Save or Remove an Explore Release

After completing the version mode and target version selection, click Save. Click Cancel to abandon the changes.

If the resource should no longer be offered to users, click Remove from Explore to remove the current Explore Release. This operation does not edit the resource definition or published versions in Resource Hub.

9. Post-save Verification

After configuring the Explore Release:

1. Return to the resource list and search for the target resource name;
2. Select the resource type category and confirm that the resource appears in the correct category;
3. Verify Published resource, Type, and Current version;
4. Verify that Visible roles matches the confirmed Role scope;
5. Verify that Version mode matches expectations;
6. In Display, verify the icon, name, description, and display order;
7. Use a test account with the target Role to enter Explore and confirm that it can discover and open the resource;
8. Use a test account outside the visible Role scope to confirm that the resource does not appear in Explore;
9. With Always use latest version, publish a validated new version and verify the current-version switch;
10. With Specific version, publish a new version and verify that the current version remains the specified version.

10. Completion Criteria

• The Explore Release is associated with a published immutable resource version in Resource Hub;
• The Explore card's icon, name, description, and display order are accurate;
• The Role visibility scope is saved and meets the organization's distribution requirements;
• The version mode is explicitly selected and saved;
• The resource appears in the correct Explore category and list position;
• Users with the target Roles can discover and use the resource;
• If the Connector requires authorization, the user Connection, connection test, and minimal capability-call path have been verified;
• Resource files, version content, and user-side access policies in Resource Hub were not modified by Explore Management.