Author Teams

You can create author teams to restrict editing of content to members of a specific team. Learn more about how to use them.

What are author teams?

If authors have editing privileges, by default, they can edit all content in your knowledge base.

However, there are times when you'd like to be able to segregate who can edit which content. This is what Author Teams are for!

Any content that is restricted to one or more author teams can only be edited by authors who belong to that team.

Any content that is not restricted to any author teams can be edited by all authors with editing access on that knowledge base.

Pro tip: If you are a full account admin and you'd like to keep editing privileges for all content, you should assign yourself to ALL author teams.

Use cases for author teams

Editors & Writers from different departments or teams

One of Linus's knowledge bases captures information for multiple departments across different lines of business. He has designated editors for each line of business:

  • Owlbus Dumbledore: Flight & Aerodynamics; owns and manages content in the "Feathers & flight", "Aerodynamics", and "Flight Tips for Owlettes" categories
  • Minerva McGonagowl: Nest building & Structural integrity; owns and manages content in the "Nest building", "Camouflage", and "Structural integrity" categories
  • Owl Pacino: Defense & Food sources; owns and manages content in the "Home defense", "Hunting", and "Food sources" categories

Each of these editors is responsible for different categories in the knowledge base and might also manage contributions from various writers.

To keep these editors from accidentally or intentionally editing each other's content, Linus has created three Author Teams:

  • Flight & Aerodynamics - assigned to Owlbus Dumbledore and all of his writers
  • Nest building & Structural integrity - assigned to Minerva McGonagowl and all of her writers
  • Defense & Food - assigned to Owl Pacino and all of his writers

He's then restricted each of his top-level categories to one of these teams. All subcategories and articles will inherit that author team restriction.

Finally, Linus assigned himself to all three of those author teams, so that he can make any final edits to all content.

Restrict single category

In another knowledge base, all of Linus's editors have access to all content. But his boss would like to add a section for HR staff to add HR materials. This content should only ever be updated by HR staff. HR staff can still update other knowledge base articles, though.

To solve this, Linus has created one Author Team called HR. He's restricted the HR category to this team--and nothing else.

All authors who have no author teams can update all content that isn't restricted, but they won't be able to touch the HR content. HR members will be able to update all other content as well as the HR category.

If Linus needs access to edit/oversee that content, he should also add himself to the HR author team.

Prevent contractor from editing other content

In our support knowledge base, Linus would like to give access to an independent security consultant to update our security policies. This author needs to be able to edit only the security policy content and nothing else. All other authors should be able to edit both the security content AND the rest of the content.

In this case, Linus needs to create two author teams: 

  • one for his security consultant, called "Security team"
  • one for all other authors, called "All content"

He'll restrict all categories to the "All content" team; he'll restrict the Security Policy category to both the "All content" team and the "Security team". He'll add himself to both teams, just to be safe.

Because all content is restricted to a specific team, and all other categories are NOT restricted to the Security team, the security consultant will only be able to edit the security category.

Because all categories--including the security category--are restricted to the All content team, authors with that author team will still be able to edit all content.

Create author teams

You must have Full Admin Access to create author teams.

To create a new author team:

  1. Click on your profile icon/name in the upper right.
  2. Select Authors from the dropdown to access the author details for your account.
  3. Open the Teams tab.
  4. Click on the + Add Author Team button.
  5. In the Create Team pop-up, give your team a Name and click the Create Team  button.

Once your team is created, you can add authors to the team and restrict categories or articles to editing by that team.

Change the order of author teams

To set the order of your author teams:

  1. Go to Your Account > Authors.
  2. Click on the Teams tab.
  3. Use the up arrows next to your team names to reorder the teams.
    Use the up arrow in the Actions section to reorder teams

Once you're done making changes, you'll see those changes reflected:

Restrict content to author teams

You can restrict entire categories or individual articles to editing by one or more author teams.

If you restrict a category to editing by specific author teams, all content within that category (subcategories + articles) will inherit the same author team restrictions.

  1. Open the category or article in edit mode.
  2. In articles, look for the Restrict to Teams section. In Categories, look for the Restrict Editing to Teams section.
    Article Editor Restrict to Teams section
    Category editor Restrict Editing to Teams section
  3. Check the boxes next to the teams you'd like to restrict this content to.
  4. Save your category or article.

Author team restrictions set at the category level will be inherited by all articles in that category.

Inherited author team restrictions

If you restrict a category to Restrict content to author team, that restriction is automatically applied to all articles within that category.

This means several things:

First: articles within that category will all be editable by only the author teams set for the category overall. You cannot add additional author teams to individual articles; they must be added at the category level.

You'll see this expressed in the Restrict to Teams section, since articles with these inherited author team restrictions will only list the author teams that the whole category is restricted to. (They'll be missing checkboxes for any other author teams in your knowledge base).

In the knowledge base we're considering, there were three author teams:

  • Team C
  • Team A
  • Team Z

If I restrict a category to Team C and Team A, when I open an article within my restricted category, I'll only see those two author teams listed in the checkboxes:

Sample article with inherited author team restrictions for Team C and Team A

When collapsed, the summary for the section will list these inherited teams (unless you have further refined the author team restrictions; see Third, below). So in this case, the collapsed section summary text will list both Team C and Team A.

Second: I don't need to select any boxes for the article to be restricted to all the author teams as the category is: it already carries the same restrictions.

Third: The checkboxes in the article editor instead allow you to further refine the author team restrictions.

If I make no selections, the article will only be editable by the author teams inherited from the category (in this case, the Team C and Team A teams). Those teams will be displayed in the summary text if the Restrict to Teams section is collapsed.

But if I do check one of these boxes, it will further restrict the article so that it is only editable by the team(s) I select. When checkboxes are selected in this way, the summary section will display only the selected teams.

So if I select "Team C" here, anyone in Team A will no longer be able to edit this article, though they'd still be able to edit other articles in the category. Only Team C will be listed in the summary text if the section is collapsed.

Removing author team restrictions

Removing author team restrictions depends on how the restriction has been set.

Author team restrictions can be set:

  • Directly on an article itself, using the Restrict to Teams checkboxes
  • Inherited from the category the article's within, no further refinements (no boxes checked in the article's Restrict to Teams section)
  • Inherited from the category the article's within AND further refined/limited to a subset of those teams (boxes checked in the article's Restrict to Teams section)

Direct restrictions

Author team editing restrictions that have been added to the article directly (and aren't inherited from the category) can be removed by unchecking the team's checkbox in the Restrict to Teams section of the editor and saving.

Inherited restrictions, no refinements

If an article has inherited author team restrictions from the category, the only way to remove the author team restriction is to remove it from the category itself.

As long as no Restrict to Teams boxes have been explicitly checked in the article itself, removing from the category will totally remove the author team restriction from the article. If any boxes have been checked in that section for the article, see the next section.

Inherited restrictions with refinements

If an article has inherited author team restrictions from the category AND has boxes checked in the Restrict to Teams section, removing the restrictions is a little more complicated.

In this scenario, you'd need to remove the author team:

  • From the category's Restrict Editing to Teams section
  • From the article's Restrict to Teams section