Help Center
Back to Altyaa

Asset Library

Per-org photo store that feeds the cockpit composer and surfaces coach-recommended media inline.

The Asset Library at /home/media is the per-org store of photos the cockpit composer publishes to Google Business Profile. Each org sees only its own assets. Uploads dedupe by content hash so re-uploading the same bytes returns the existing row.

Uploading your first photo

Open /home/media from the Grow section of the sidebar and either drag a file onto the dropzone or click Upload to pick one.

  • Supported types: JPG, PNG, WebP, MP4.
  • Maximum size: 25 MB per file.
  • One file at a time. Bulk import is on the roadmap.

Uploads land in the library as Scanning and flip to Ready once magic-byte verification and dimension extraction complete (typically under two seconds). The tile auto-refreshes; no manual reload needed.

Dedupe behavior

The library is content-addressed per organization. If you upload the same bytes twice — same photo, same export, same screenshot — the second upload collapses into the first row. The original Uploaded by and Created at are preserved. This is per-org: two different organizations uploading the same photo each get their own row.

If the second upload is the same bytes under a different filename, the row is still reused; rename does not create a duplicate.

Filtering and finding assets

The filter rail above the grid threads through the URL, so a filtered view is shareable and survives reloads.

Status

FilterShows
AllEvery non-deleted asset
ReadyScan complete, safe to publish
ScanningStill in the async scan pipeline
RejectedScan failed — see Why was my upload rejected?

Source

FilterShows
All sourcesOperator uploads and coach-ingested URLs
Uploaded by youOperator uploads only (source=OPERATOR_UPLOAD)
Coach-suggestedPhotos materialized from a coach recommendation (source=COACH_URL_INGEST)

The pipeline radiator above the grid shows the rolling 24-hour count for Uploaded, Scanned, Published, Coach-attached, and Failed. Collapse it via the chevron; the collapsed state persists per-browser.

Using coach-recommended media

When a coach attaches photos to a daily recommendation, those photos render inline in the recommendation detail sheet as a 96×96 thumbnail strip. The same photos also appear in the library with the badge so you can find them later.

Coach-suggested

From the detail sheet

  1. Open your daily recommendations and expand any one that has a thumbnail strip.
  2. Click any tile to open the lightbox preview.
  3. Click Use in composer to open the publish modal with the asset pre-attached and the recommendation's title carried into the caption draft.

If the coach's URL ingest succeeds, the asset already exists in your library by the time the recommendation lands. If it fails, the recommendation still shows — the text-only recommendation is the fallback. The recommendation sheet never blocks on media resolution.

Dismissing a suggestion

The strip is informational. Closing the recommendation sheet without clicking Use in composer is the dismissal. Coach-suggested assets remain in the library under the Coach-suggested source filter until soft-deleted.

Permissions and roles

Three RBAC permissions gate the media surface. Defaults below; per-org overrides via custom roles.

PermissionOwnerAdminMember
media:uploadyesyesyes
media:publishyesyesyes
media:deleteyesyesno

WS-1 grants media:delete to Owner and Admin only. The Member grant is revisited in WS-2 once the audit-log retention pipeline is shipping for at least one release.

Search documentation

Search through help articles and documentation

  • Features
    • Asset Library
    • Publishing to Google Business Profile
    • Channel states in the cockpit
    • Connecting Facebook Pages
    • Why was my upload rejected?
    • Connecting an Instagram Account