Skip to main content

Author spaces

An author space is a content scope below an account’s public path. It can represent a person, a blog, a section, an archive, or another bounded publication area.

The Username/Author value is both the login username and the default public author path. It uses lowercase letters, numbers, and underscores and cannot be renamed through ordinary user editing after creation.

Content ownership

Authors create posts and pages in their own space. Superadmins can create root content or select an existing author as the owner in Full Composer mode.

Author pages form their own hierarchy. Posts remain in the author stream. Tags, search, feeds, media ownership, and secret links respect the author scope.

Root aggregation

An author post can opt into the root stream through Aggregate to root. This makes the post eligible for the site listing; it does not change its canonical author-space URL or ownership.

The author’s default aggregation choice seeds new posts and does not rewrite existing entries.

Appearance

Author spaces inherit the site theme by default. Profile > Appearance can select another available theme and supported overrides such as content width, screen mode default, banner, background, and theme-specific behavior.

Leaving an override blank uses the site setting. Author spaces currently inherit the global Primary and Footer menus.

Publishing settings

Profile > Publishing holds the author’s new-content type and status defaults, root aggregation default, indexing preference, and author secret link. These defaults apply to newly created content only.

Locked accounts and sections

Account access and public content are controlled separately:

  • disabling Account enabled prevents sign-in and invalidates the account’s sessions
  • disabling Public content enabled hides the author space and suspends its secret link

A superadmin can therefore maintain a published author space whose account cannot sign in. Deleting the user is different: the user record is removed, its secret link is revoked, and owned content moves into orphan storage for explicit review.