Checking and integrations
Privilege |
Description |
---|---|
|
Check content with Acrolinx. |
|
Discover terms when you check. You need this privilege to discover terms with the Terminology Tab in the Sidebar. |
|
Add to the spelling exception list. You can add words to a permanent spelling exception list from the Sidebar. You might need to restrict access to spelling exception lists. |
|
|
|
Access the extracted text in an integration. This feature is implemented in the Content Analyzer — just add the column "Extracted Text." |
|
Access the Classic Reuse API. |
|
Use the Term Transfer Tool. |
|
Manage Checking Profiles in Acrolinx. |
|
Open a Scorecard or the Content Analysis Dashboard. |
|
Use the options for AI writing help described in the AI Assistant Quick Start and in How to Use AI Writing Help in the Sidebar. |
Content Cube
Privilege |
Description |
---|---|
|
NoteYou'll only get this privilege if Content Cube is included in your license. |
Dashboard
Privilege |
Description |
---|---|
|
Access Acrolinx with a username and password. |
Guidance
Privilege |
Description |
---|---|
|
|
|
|
|
Assign reuse repositories to Writing Guides. |
|
Reload a language configuration from the Language servers section. |
|
|
|
NoteYou’ll only get this privilege if you have style guides enabled. |
|
Access the Style guides section. You can't edit style guides with this privilege, but you can view style guides, style guide assignments, and current settings. NoteYou’ll only get this privilege if you have style guides enabled. |
Analytics
Privilege |
Description |
---|---|
|
View the Analytics Dashboards and open the Content Analysis Dashboard. |
|
Create Custom Dashboards in Analytics. |
|
Manage Acrolinx Analytics including Content Groups, Content Recognition and more. |
Reuse
Privilege |
Description |
---|---|
|
Create and edit sets in Reuse. Learn more in the Reuse Quick Start. NoteYou’ll only get this privilege if you have Reuse enabled. |
|
Access and view sets in Reuse. You can't edit sets with this privilege, but you can view sets and current settings. Learn more in the Reuse Quick Start. NoteYou’ll only get this privilege if you have Reuse enabled. |
Servers
Privilege |
Description |
---|---|
|
|
|
|
|
|
|
|
|
|
|
View the list of servers in the Language servers section. |
|
Access to monitoring API endpoints. |
Terminology
Privilege |
Description |
---|---|
|
|
|
Edit terms. You can add a restriction for language and domain. |
|
|
|
|
|
|
|
|
|
|
|
Customize the terminology section and adjust the term variant exceptions. |
|
Term Browser
Privilege |
Description |
---|---|
|
Access the term browser with a username and password. |
Term contribution
Privilege |
Description |
---|---|
|
Access the Contribute a term pagewith a username and password. You'll also need this privilege to contribute terms from the Terminology tab in the Sidebar. |
|
Add additional comments to existing terms in the term contributor. |
|
Remove comments from existing terms in the term contributor. |
Users and roles
Privilege |
Description |
---|---|
|
View the list of users and roles in the Users section. NoteOnly users with the Super Administrator role can edit roles. Learn more about roles. |
|
Edit users in the Users section. |
|
|
|
Create an API token in the Users section. |
If you use Acrolinx to manage terms for different languages and domains, you might want to ensure that your translators and terminologists can only edit the terms and term settings that are relevant to their role. To do this, add restrictions to the privileges so that users can only edit a term if the term is associated with a specific language or domain.
You can add restrictions to the privileges that enable users to Edit terms and to Change the status of a term. These privileges appear in the Terminology section of the Edit role page. You can only add one language or domain for each restriction. To restrict a user to more than one language or domain, give the user multiple roles with the relevant restrictions.
When working with these restrictions, it’s important to understand where Acrolinx stores term information. Suppose that a head term is English and your translator can only edit the German translations of this term. Some of the term information only applies to the relevant language. The translator can therefore edit this language-specific information. Other term information is stored in the English head term and "passed on" to the German term. The translator with a restriction for German terms can't edit this information — because for Acrolinx, it’s in English.