> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.writesonic.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Authors
> Define who can appear in a byline, what supports their authority, and what they're allowed to say.
Authors sits inside Brand Kit. Each entry represents a named individual or the company itself, with a **Type** field distinguishing the two. The section shows when each entry was last edited and includes an **Add author** button for creating another.
## The profile fixes an identity behind every byline
A byline needs more than a display name. The identity fields establish who the author is, where they work, and how their name should appear publicly.
**Name** identifies the profile inside your workspace. **External name** holds the exact name shown on the author's public byline, while **Title** and **Company** supply the professional context around it.
Turn on **Primary** to "Make this the default author whose byline is used unless another is chosen." We recommend setting one primary author so tasks don't fall back to an unspecified byline.
## Three bio lengths keep the same identity usable
Each profile holds three bio variants at about 50, 100 and 200 words. That gives the agent an appropriate version for a compact byline, a standard author box, or a page that has room for a fuller background.
The three versions should tell the same story at different depths. Keep the name, role and main area of expertise consistent, then use the longer versions to add supporting experience.
## Credentials turn the byline into an E-E-A-T record
**Education**, **Previous roles**, and **Notable** capture the evidence behind the author's authority. Previous roles record both the company and the role, so the profile can carry relevant career experience instead of relying on a broad claim of expertise.
This is the **E-E-A-T record** behind the byline.
Use **Notable** for specific work, recognition, or experience that helps explain why this person can credibly cover the subject. Add **LinkedIn**, **Twitter**, and **Website** under Social so the public identity can be connected to its source profiles.
## Permissions keep founder and company bylines distinct
Permissions decide what an author is allowed to do in generated content. Each one is a toggle with a plain description, covering things like making predictions, taking contrarian positions, sharing personal opinions, telling company stories, speaking for the company as "we", making direct recommendations, criticising competitors, and discussing pricing.
One real profile allows predictions, company stories and direct recommendations, and keeps contrarian positions and personal opinions off. That suits a named founder whose experience supports a forecast but whose published work shouldn't pick fights. A company byline can answer every one of those differently.
**Disclosure** sits alongside them. It sets whether content from this author has to carry a disclosure, and what form that disclosure takes.
## Hard prohibitions stop the author crossing known lines
**Things this author would never say** is a list of statements that generated content must avoid. It records explicit boundaries that broad voice guidance can miss.
Two real entries from one profile: "SEO doesn't matter anymore" and "Traditional search will never change".
Write them as direct statements the author rejects. That gives the agent a concrete prohibition instead of asking it to infer one from tone.
## An author tag carries the profile into a task
When a task should use a particular byline, tag the author into the task to write as them. The identity, biography, credentials and permissions then travel together as one profile.
See [tagging context](/agents/tagging-context) for how to add that author alongside the task's other context.
## What's next
Define the register an author should use.
Add an author profile to a task.