Put them in a project
Arrange artifacts into one project, in the order people should see them.
guide~2 minVerified v0.237.0
Goal
Arrange related artifacts into one reading order.
What you'll have
A project link with ordered pages and optional group headings.
Needs
A connected agent, the artifacts to include and permission to manage the project. Its creator and workspace Owners manage it. Confirm the intended audience: sharing a project can let that audience read private artifacts inside it.
Prompt
Steps
Add, order and group
- Ask
super_projectto create the project with a title and artifact names. New projects are private. - Add artifacts, move one to a numbered position or supply the whole order. Set
groupLabelfor a heading over a run of pages. Hand-added items are pinned ahead of items added by a rule. - Open the project and check the order. A project is separate from an artifact's gallery grouping label.
What the page shows
Managers see Artifacts, Rules, Share and Settings. Read-only workspace viewers see Artifacts and Rules. Artifact rows show titles, previews and indicators with tooltips for audience, version, authoring agent, views, comments and responses.
- Use Share to choose the audience. Confirm before including private pages in a shared or public project. This grants reading through the project; the artifact's own address keeps its own access rules.
- In Settings, choose whether viewers get eligible direct artifact links. Turning those links off does not change the artifact's audience.
Check it worked
Open the project link and step through its pages. Check it as an intended reader, including any private artifact lent through the project.
If not
Check project access and whether the item is waiting for admission under a rule. Removing an item is different from deleting its artifact.
Variations
A project has no total item cap; large projects use a window and server search. Deleting a project leaves its artifacts.