Catalog
The catalog lists the Deployables in your organization. It answers “has someone already built this?”, a question people only ask when there’s somewhere to ask it.
What appears in it
Section titled “What appears in it”Everything except Deployables scoped to Only me. A tool shared with specific people and groups is listed for the whole organization even though only that list can open it: everyone else sees that it exists and can request access from the owner.
Guests don’t see the catalog at all.
Finding things
Section titled “Finding things”Entries carry a name, description, owner, and tags, and can be searched and filtered by tag or owner. Tags are shared across the organization, so a tag someone else added is one you can filter by.
Writing an entry worth finding
Section titled “Writing an entry worth finding”The description is the entry. Say what the tool does and who it’s for: “Weekly pipeline numbers by region, refreshed each Monday, built for EMEA sales” works; “Sales dash v2” doesn’t. Lead with the problem, since people search for their problem rather than your tool’s name. Say where the data comes from and how fresh it is, which is the first thing anyone asks. Skip the implementation.
Tag consistently. Two spellings of the same idea split a filter in half.
Keeping it honest
Section titled “Keeping it honest”A few stale entries teach people not to trust any of them. Keep ownership current, and prefer group ownership for anything a team depends on, so a tool doesn’t quietly become unmaintained when its author moves on.
Search before you build. Ten seconds occasionally saves a week.
