Social and Community Content

User-Generated Content Permission Record

Document informed creator permission, identity verification, content scope, channels, edits, credit, compensation, duration, withdrawal, and final usage.

Free editable Markdown · Community teams, rights managers, and social media teams · Updated July 30, 2026

Download Markdown

Accessible HTML preview

Blank template

The downloaded file contains the same fields in editable Markdown.

Asset and creator

Rights record ID: [Unique reference]
Asset description: [Image, video, text, audio, or another]
Original post or file: [Controlled location]
Creator name or approved credit: [Value]
Control verification: [Method and date]
Other identifiable people: [Permission status]
Third-party rights: [Music, artwork, venue, employer, or another]
Sensitive context: [Minor, health, location, crisis, or another]
Specialist reviewer: [Role if required]

Permission request

Requesting organization: [Legal or public name]
Purpose: [Editorial, community, promotion, advertisement, or another]
Channels: [Exact websites, accounts, email, print, or another]
Territory: [Countries or global]
Duration: [Dates or defined period]
Paid promotion: [Included or excluded]
Allowed edits: [Crop, captions, translation, excerpts, or none]
Credit and link: [Exact form]
Compensation or exchange: [Amount, product, none, or another]
Withdrawal process: [Route and practical effect]

Decision evidence

Request sent: [Date, channel, and approved text]
Questions answered: [Record]
Affirmative permission: [Exact response and date]
Restrictions: [Creator conditions]
Verification completed by: [Name or role]
Evidence location: [Restricted store]
Expiry or review date: [Value]

Consent was not inferred from a tag, hashtag, silence, or unrelated submission.
The final planned use matches the request the creator saw.
Unnecessary identity information was not collected.

Publication and withdrawal

Approved asset version: [File reference]
Edits made: [Exact list]
Disclosure: [Creator, partnership, incentive, or another]
Published locations and dates: [Inventory]
Downstream owner: [Role]
Withdrawal received: [Date or none]
Action taken: [Stop, remove, retain under terms, or another]
Copies outstanding: [Reason and owner]
Record retention date: [Rule]

How to use this template

Identify the creator, original asset, source location, other people or rights, and any safeguarding or specialist-review need.
Send a clear request describing organization, purpose, channels, promotion, edits, credit, compensation, territory, duration, and withdrawal terms.
Verify the responder's control through an approved low-data method and capture an affirmative decision without preselected consent.
Link permission evidence to the approved file, allowed uses, edit boundaries, disclosure, expiry, and a unique internal rights identifier.
Check scope before every publication or reuse, record live locations, and act on expiry, correction, dispute, or withdrawal.

Ask for specific and understandable permission

Identify the exact asset, creator, original location, and people or protected works included. Explain who wants to use it, where, for what purpose, whether promotion or paid advertising is included, how long the use may continue, and which regions apply. Avoid a vague reply such as “Can we share this?” when the team intends to crop the image, add promotional copy, translate it, place it in an advertisement, or archive it indefinitely. Use language the creator can understand and provide an accessible way to ask questions before agreeing.

Confirm rights, edits, credit, and value

Verify control through the original account or another approved method without collecting excessive identity data. Ask whether a photographer, musician, employer, venue, or depicted person has rights that the uploader cannot grant. Record allowed edits separately: crop, resize, caption, subtitle, color adjustment, quotation excerpt, translation, or combination with other material. Agree on credit wording, link, anonymity request, compensation, product, contest terms, or another exchange. Permission should not be assumed from tagging a brand, using a campaign hashtag, or submitting a support request.

Control use after approval

Store the permission evidence, approved asset, final edits, published locations, expiry, and withdrawal instructions in a restricted record. Give publishers a clear use ID so they can check scope without reading private correspondence. Before each reuse, confirm that channel, purpose, territory, duration, edit, and disclosure remain allowed. When a creator withdraws permission, follow the agreed terms and applicable requirements, record the request, stop future scheduling, and identify copies that can or cannot be removed. A consent record is useful only if downstream teams can find and honor it.

See the fields in context

Fictional example: community garden photograph

Rowan Street Garden, its member, and the photograph described here are invented.

Request: The fictional garden asks the adult photographer to use one named image in an unpaid event recap on its website and two owned social accounts for twelve months.
Rights check: The photographer confirms authorship; two recognizable adults depicted separately approve the stated use.
Edits: Permission allows resizing and an accessibility description, but not filters, advertising, or removal of the visible project sign.
Credit: The approved caption credits the photographer by chosen display name and links to the community page.
Control: The rights ID is attached to each scheduled version, and the owner must seek new permission for a future fundraising advertisement.

Frequently asked questions

Is mentioning the brand enough to grant permission?

No. A mention or hashtag can invite attention without granting reuse rights. Ask explicitly and describe the intended use so the creator can make an informed choice.

Can one permission cover all future channels?

Only when the approved terms clearly say so and that scope is appropriate. Broad indefinite language may not reflect informed expectations. Specific channels, purpose, duration, and edits make compliance easier.

What if several people appear in the asset?

The uploader may own the file without controlling every person's privacy, publicity, or consent interests. Assess each identifiable person and the context, especially minors or sensitive settings, before use.

Does deleting the original post cancel permission?

Not automatically; follow the agreed terms and applicable rules. Treat deletion as a reason to check context and contact the creator when appropriate. Preserve only the minimum evidence needed for the decision.