Access, protected instructions and AI labels
Your studio account, its API key permissions and an explicit sharing action determine what another client can access. A model choice or a copied project title does not grant access to private work.
Project links, media links and recipes differ
Section titled “Project links, media links and recipes differ”A project URL identifies a project; the signed-in account must still be allowed to open it. An MCP agent uses its key’s account and scopes. Do not give it another account’s key merely to resolve a missing project.
An artifact can have an authorized download link with an expiry. If it expires, obtain a fresh link with the supported artifact tool. Share links and downloaded files can have different visibility from the private project they came from. Inspect what you intend to share before sending it.
A recipe describes reusable work. It is not unrestricted access to the author’s private project, account or media. The recipient reviews the inputs they need to supply. See sharing and reuse and files and artifacts.
Public cards and protected instructions
Section titled “Public cards and protected instructions”System skills expose useful metadata such as their name, purpose, targets and version. Their protected instruction bodies are not returned to an ordinary client. Applying a skill can work even when its implementation text is hidden.
Other built-in reusable content can have a public body while remaining read-only. Public visibility and permission to modify the built-in original are different. Use the library’s supported copy or personal-item workflow when available; do not infer edit permission from being able to read an item.
Administrative settings and internal debugging traces are separate from the ordinary studio and MCP views. This documentation explains supported behavior and safe examples; it does not reproduce protected system instructions or private infrastructure routing.
Review AI disclosure before publication
Section titled “Review AI disclosure before publication”The TikTok and YouTube publishing forms offer a Made with AI control. Review that control along with the destination, visibility and other declarations for the actual material you are publishing. The current YouTube form starts with AI disclosure enabled.
When sending a TikTok draft, finish its description and declarations in TikTok. A draft transfer does not carry every choice from a direct-publication form.
The existence of a checkbox does not certify a clip’s provenance or satisfy every obligation for every use. This page describes the studio controls. Follow the destination’s current instructions when choosing what to disclose. See publish a video for the workflow and confirmation step.
Resolve an unexpected access error
Section titled “Resolve an unexpected access error”Check the account, project, key permissions and whether a temporary link has expired. If a protected field is absent, use its public card and supported action rather than asking an agent to extract hidden instructions. Report a persistent mismatch with the operation and visible error, without including your secret key.