---
name: access-content-factory-source-assets
description: "Get the right access to the photos and videos for your task. Check that you can open the actual files."
category: Content Factory — Produce
stage: Produce
definitive_article: https://blitzmetrics.com/access-content-factory-photos-videos/
status: needs-work
---

# Access Content Factory source assets

You need the right files before you can start a job. This guide helps you find the photos and clips your team needs. Start with the job name and file list, then check that each file will open.

**The path:** Known task and files → Approved access → Open real sources → Handoff.

**Use this when:** An assigned content task needs specific photos, videos, or project files that are not yet accessible.

## Inputs
- The assigned project and task, your work email, the files or dates you need, and the intended use.
- The project’s current access contact and approved invitation or credential-sharing method. The public guide names an operations contact and LastPass; confirm that this is still the approved route for this project.
- The exact Basecamp project and known asset locations. The source names Google Photos, Drive, and Dropbox, but this task grants no access to unrelated libraries.
- A way to record safe file references, access results, and blockers without copying passwords, recovery codes, or private customer content.

## First-run prompt

> Use my assigned project, file list, and approved access method to build an access checklist. Prepare a narrow request if needed, but do not send without authority. Check each actual file and separate viewing, downloading, editing, and publication rights. Report exact blockers without storing or exposing secrets.

## Steps
1. Write the access scope before asking: project, task, work email, specific source files, intended use, and the role you need. Ask the project’s known access owner to confirm the current method. Do not use a public article’s historical shared-login email as a credential instruction.
2. Prepare the request for the approved operations contact. Send it only within the authority of the actual job. A draft request is not an invitation, and an invitation is not working access.
3. Accept the genuine project invitation. If the access owner confirms LastPass is still used, accept that invitation into the approved account and use the shared item for this project. If the project uses direct account access instead, follow that invitation. Do not create a second credential store or put secrets in the tracker.
4. Open the assigned Basecamp project through the confirmed link. Check the task, source-file instructions, and allowed uses. Use [Basecamp Basics](https://localservicespotlight.com/basecamp-basics-the-foundation-of-how-we-work/) for the team’s project workflow; it is a reference, not a grant of access.
5. Open the confirmed source location. In Photos, search by the supplied person, date, place, or event; in Drive or Dropbox, follow the exact project folder. A search result with a similar name is only a candidate: compare the source date, subject, and task.
6. Check the actual required files one by one. Confirm the photo or video is the intended source, the original or allowed copy is available, and your role permits the needed next action. Keep video muted at volume zero; use metadata, still frames, or captions if silence cannot be verified before playback.
7. Log file reference, system, expected action, observed access, date, and any use limits. Distinguish “can view” from “can download,” “can edit,” or “may publish.” These are separate checks, not one yes/no permission.
8. For missing access, record the exact denied location or missing file and send the smallest request through the current authorized project route. Do not widen sharing, seek another person’s login, or infer that every asset is cleared.
9. Hand the verified source list to [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript) or the specific assigned processing task. Report completion in the project thread only when sending is authorized. Keep inaccessible files as blockers, and write the run record even when access is incomplete.

## Definition of done (QA checklist)

- [ ] The project, task, files, intended use, and requested role are explicit.
- [ ] The assigned project opens and the actual required source files have been checked.
- [ ] View, download, edit, and publication rights are distinguished according to the task.
- [ ] Missing files or access are recorded precisely; no historical login detail is treated as current proof.
- [ ] The handoff contains safe file references and limits, with no secrets.

## Example(s)

**Fictional teaching example — no access was requested or granted.** A sample assignment asks an editor to use two Maple Cycle photos and one recorded shop tour.

| Needed item | Sample observed state | Next action |
| --- | --- | --- |
| Shop front photo | Can open the intended file; use approved for the draft | Pass its private file reference to the editor |
| Owner photo | Search finds two people with the same first name | Ask the project owner to confirm identity |
| Shop tour | Folder opens, but the video cannot be downloaded | Ask for the role needed for the stated editing task |

The sample result is one verified source, one identity question, and one access blocker. “The folder opens” would hide two unfinished checks. No password, shared-login address, or private file URL belongs in a public meta article.

## Handoff and Content Factory context

The assigned editor gets the verified source references and use limits. [Upload the source to Drive and Descript](https://local-service-spotlight.github.io/task-library/?task=step-1-upload-video-to-google-drive-and-descript#task-step-1-upload-video-to-google-drive-and-descript) is the common next task; use another processing task only when the assignment names it. The project access owner resolves permissions, not the drafting agent.

This task serves **Produce** in the [Content Factory](https://blitzmetrics.com/content-factory/). Produce makes or prepares source material. Process edits it, Post puts approved work on a channel, and Promote helps it reach people. Only the steps and handoff above are part of this task.

## When this runs

Run for each new task or changed access need. Recheck required files when permissions change. The source establishes no automatic access-monitoring schedule.

## Run with an agent

The agent can prepare the plan, organize allowed files, and check the evidence it can actually access. A person records real stories, supplies permission, or resolves an account step when needed. Save the current state in the project files and tracker. A model name does not create memory, access, a scheduler, or permission to act.

For all agent media checks, keep the player muted and its volume at zero before playback. If that cannot be checked, use captions, metadata, or still frames. Do not claim sound quality was heard when it was not.

## Write up the real run

For every actual attempt, [write the run’s meta article](https://blitzmetrics.com/meta-article-prompt/). Link this exact task and its source revision. State the start, work done, evidence, result, gaps, and next owner. Keep failed, partial, and blocked work visible. Writing the record does not authorize publishing it.

Use one stable execution ID for this task’s actual run. Internal retries, checks, and new versions do not add runs. A separately scoped child task may have its own ID linked to the parent. A teaching example has no real execution ID and must not enter the run count. Follow the [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) for that distinction.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Produce
- **Importance:** 3/5 `●●●○○` — frequency 3, revenue 3, gating 2 (supporting)
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Raw files in Content Library `01-Raw/` plus a tracker row (question, date, speaker). Next skill never needs the chat — it needs the files.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Canonical article: https://blitzmetrics.com/access-content-factory-photos-videos/
- Exact task: [Access Content Factory source assets](https://local-service-spotlight.github.io/task-library/?task=access-content-factory-source-assets#task-access-content-factory-source-assets)
- Publishing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)

## Review and evidence still needed

The contributor status in the source header is preserved. It is not a claim that this draft has been independently accepted or that a real run has passed. The worked example above is for teaching only.
- The current operations contact, credential method and account permissions require confirmation by the real project access owner.
- No live account access or invitation was tested in this draft batch.