Admin pages

Workspace owners and admins see Admin under System in the sidebar, in both the web library and the desktop app. It has tabs for Dashboard, Users, Denylist, Webhooks and Maintenance. People are invited to the workspace from your prophouse.dev dashboard, not here; see Workspace and members.

Admins also get extra actions on each prop’s page: Deprecate, Add to denylist and Delete asset…. See Prop detail page.

Dashboard

Counters for the library at a glance, in three groups:

Group	Counters
Catalog	Assets (active and deprecated), objects (versions), lineages, packs, collections, tags and users
Storage	Blobs, blob bytes, object bytes, logical bytes and the Dedup ratio (how much space identical files save)
Pull queue	Queue depth and the number of pull jobs in each status

Users

The Users tab lists everyone and every key that has used this library, with display name, Role, Kind (person or service account), status and creation date. Rows appear automatically as people and keys use the library. To invite someone or create an API key, use Members and API keys in your dashboard at app.prophouse.dev.

For each row you can:

• Edit the display name.
• Change the Role between Member and Admin.
• Disable or Enable the account.
• Delete it, after confirming.

Denylist

The denylist blocks content at push time. Use it when something must never enter the library again, for example an asset that leaked in by mistake.

There are three kinds of rule:

Kind	Blocks
Content hash	Exactly these bytes (a SHA-256 hash).
Lineage	Every version of a cataloged prop, including future edits of it.
Package GUID	Edited copies of an Unreal package that were never cataloged.

The quickest way to block a prop is Add to denylist in its More actions menu, which adds all three rules at once. To add a rule by hand, pick the kind, enter the value and an optional reason, and click Add rule. Remove, then Confirm remove, deletes a rule. Export CSV saves the list.

Webhooks

Webhooks send workspace activity (pushes, locks, reviews, comments and more) to your own HTTPS endpoint or a Slack channel.

1. Enter the Webhook URL. It must start with https://.

2. Choose the format: JSON (signed) for your own receiver, or Slack incoming webhook for Slack.

3. Optionally enter a secret; leave it blank to have one generated.

4. Optionally expand Events and pick which events to send. With none checked, all events are sent.

5. Click Add webhook. Copy the signing secret from the dialog: it is shown only once. Your receiver uses it to verify the X-PH-Signature header.

Each webhook row has Test (sends a test event and reports the result), Deliveries (recent attempts with status, attempt number, next retry and error), Pause / Resume, and Delete. Failed deliveries are retried automatically with increasing delays. For payload details, see the REST API section.

Maintenance

The Maintenance tab holds catalog-wide cleanup tools. Most follow a preview-then-apply pattern: nothing changes until you apply a preview you’ve reviewed.

Category taxonomy

Categories should say what a prop is (a chair, a rock, a streetlight), while Types already say what format it is. Categories derived from folder names often drift from that. This section lists every category with how many props and packs use it.

1. Click Propose cleanup to prefill suggested changes based on the recommended taxonomy, or type your own. For each category, enter a New name (blank = keep) to rename or merge it, or check Clear to remove it. Expand Recommended taxonomy to see the suggested subjects.

2. Click Preview migration to see exactly how many props each change affects.

3. Click Apply migration. Editing anything after the preview requires a new preview.

Semantic layer

Shows the embedding Model and Coverage (how many props are embedded and how many are pending), and offers:

• Preview category suggestions proposes categories for uncategorized props from their thumbnails. Keep Use recommended taxonomy (tuned prompts) checked, or uncheck it and enter a Custom vocabulary, one subject per line. Min confidence sets how sure a suggestion must be. Review the preview, then click Apply suggestions.
• Detect duplicates looks for props that look alike and adds them to Possible duplicates. For each pair, choose Keep this one on one side (the other is deprecated; nothing is deleted), Link as variants if both are wanted, or Dismiss if they aren’t duplicates. Each side shows how many other props reference it, so you know which one is safe to retire.
• Rebuild embeddings drops every stored embedding and re-embeds the library in the background. Semantic search and duplicate detection work less well until it finishes, so it asks you to type rebuild to confirm.

Pack attribution

For props with no pack, Prophouse can derive packs from their /Game/ folder structure. Click Preview pack backfill to see which packs would be created and how many files each would cover, then Apply backfill. New pushes are attributed the same way automatically.

3D previews

Re-render mesh previews and Re-render all previews queue existing previews to be generated again. The next Process Library run in the Unreal editor re-exports and uploads them; the current previews stay visible until their replacements arrive. See Previews.

Note

The Maintenance tab also contains server upkeep tools (garbage collection, integrity check, database backup and search index rebuild). They aren’t covered here.