-
Notifications
You must be signed in to change notification settings - Fork 6
/
UserRoles_Editor.dita
33 lines (33 loc) · 1.72 KB
/
UserRoles_Editor.dita
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic id="topic_mvz_rmv_bt">
<title>Editor</title>
<body>
<p>Editors may review and correct database objects owned by other users even if no specific
rights for the database object (i.e. user statuses) were granted to them. This applies to
database objects with visibility types "public" (default), "project", or "all authenticated".
In other instances (with visibility types "Reader" and "Group"), Editors have access to the
given database objects if they have been assigned the Updater or Reader status.</p>
<p><b>Rights</b></p>
<p>
<ul id="ul_v25_l4v_bt">
<li>Can edit all items in a database, i.e. the text corpus, the lemma list, or the thesaurus
database, where they have been assigned Editor rights.</li>
<li>Can add or remove database objects within a corpus.</li>
<li>Can assign the Updater or Reader status to other users, but only for individual database
objects.</li>
<li>Can change their own status as a Reader or an Updater. This is irrelevant however,
because the user role "Editor" takes precedence (as in the case of the Admin).</li>
</ul>
</p>
<p><b>Limitations</b></p>
<p>
<ul id="ul_lwp_n4v_bt">
<li>In cases where the corpus was created by someone else, Editors can modify individual
database objects, but are attributed a guest role for the corpus itself (i.e. they cannot
edit the corpus passport data, or assign Updaters / Readers for an entire corpus). </li>
<li>The Editor cannot create new corpora within a project.</li>
</ul>
</p>
</body>
</topic>