Skip to content

Commit f12c8c2

Browse files
Dmi3yyDmi3yy
committed
add
1 parent 51dc5a3 commit f12c8c2

5 files changed

Lines changed: 141 additions & 0 deletions

File tree

‎en/01_Info/01_Administration/10_Admin_Users/10_Admin_Roles_And_Groups.md‎

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
2+
<p>Using Admin Roles, Document Groups, and Admin User Groups you can control every aspect of the management of your Evo site.</p>
3+
<h3 id="AdminRolesAndGroups-BeforeYouBegin">Before You Begin</h3>
4+
<p>Make sure that "Use access permissions" is set to Yes in the User Settings tab of System Configuration.</p>
5+
<p><img src="assets/images/docs/user-settings.jpg" alt=""></p>
6+
<h3 id="AdminRolesAndGroups-ThePieces">The Pieces</h3>
7+
<p>Permissions in Evo are composed of many parts that all work together. At first, it can be a little confusing as to what all the parts are, what they do, and how they interact. For that reason, each part will be explained below, followed by an example:</p>
8+
<ul>
9+
<li><strong>Document</strong> - The fundamental element (a "page") in Evo. Each document is assigned to one or more document groups.</li>
10+
<li><strong>Document group</strong>- As it sounds. A group of documents that for some reason are placed in the same group. A common example of this would be the main sections of a site (such as Products, Portfolio, or Services). A document group can be connected with one or more user groups.</li>
11+
<li><strong>User</strong>- The user piece contains information about the specific user such as name, password, etc. The user piece does NOT define the permissions. Permissions are defined in the role. Each user can be assigned to one or more user groups, but can only be assigned to one role.</li>
12+
<li><strong>Role</strong> - As just mentioned, the role is the piece that defines the permission of any user who is assigned that role.</li>
13+
<li><strong>User group</strong>- A collection of users who will need access to the same document groups. A user group can be connected to one or more document groups.</li>
14+
</ul>
15+
<p>So how do all these work together? Roles determine what a user has permission to do, and user groups combined with document groups determine what documents a user can work with. An example will probably the be most effective way to demonstrate this.</p>
16+
<p>Suppose you have a site to distribute the software your company writes. You also want to have a discussion and help forum. You decide that your site will look like this:</p>
17+
<ul>
18+
<li>Home</li>
19+
<li>News</li>
20+
<li>Products
21+
<ul>
22+
<li>Games</li>
23+
<li>Graphics Utilities</li>
24+
<li>Project Management</li>
25+
</ul>
26+
</li>
27+
<li>Support
28+
<ul>
29+
<li>FAQ</li>
30+
<li>Forums</li>
31+
<li>Contact Us</li>
32+
<li>Live Support Chat</li>
33+
</ul>
34+
</li>
35+
<li>About Us
36+
<ul>
37+
<li>Our history</li>
38+
<li>Our philosophy</li>
39+
<li>Our people</li>
40+
</ul>
41+
</li>
42+
</ul>
43+
<h3 id="AdminRolesAndGroups-Roles">Roles</h3>
44+
<p>First, you decide you will need these Roles:</p>
45+
<ul>
46+
<li><strong>Site administrators</strong> - will manage users and general site configuration.</li>
47+
<li><strong>Developers</strong> - will create the code used in special applications, such as the Live Support Chat feature. Will handle modules, plug-ins, snippets, and TVs</li>
48+
<li><strong>Designers</strong> - will be responsible for the overall look and layout of the site's pages. Will work with templates, chunks, and CSS.</li>
49+
<li><strong>Content editors</strong> - will be responsible for the content of the pages. Will work with documents.</li>
50+
<li><strong>Proofreaders</strong> - will be able to edit, but not create or delete documents.</li>
51+
</ul>
52+
<p><img src="assets/images/docs/role3.jpg" alt=""><br>
53+
<img src="assets/images/docs/role5.jpg" alt=""></p>
54+
<h3 id="AdminRolesAndGroups-DocumentGroups">Document Groups</h3>
55+
<p>Next, consider how the documents in your site will be grouped.</p>
56+
<ul>
57+
<li><strong>Corporate</strong> - pages referring to the company in general, such as the About Us pages and the Home page.</li>
58+
<li><strong>Product</strong> - pages dealing with individual products.</li>
59+
<li><strong>Support</strong> - pages that contain FAQ lists or company contact information.</li>
60+
</ul>
61+
<p><img src="assets/images/docs/access2.jpg" alt=""></p>
62+
<h3 id="AdminRolesAndGroups-UserGroups">User Groups</h3>
63+
<p>Then you begin to organize the User groups your content editor users will belong to.</p>
64+
<ul>
65+
<li><strong>Marketing</strong> - will handle Corporate pages; anything that will effect the public's perception of the company and its products.</li>
66+
<li><strong>Products</strong> - will work with the pages relevant to the company's products.</li>
67+
<li><strong>Support</strong> - will take care of the support pages.</li>
68+
<li><strong>Proofreaders</strong> - will have access to all documents (but is limited in what he can do with them by the permissions granted by his Role).</li>
69+
</ul>
70+
<p><img src="assets/images/docs/access1.jpg" alt=""></p>
71+
<p>Here is how the user groups and documents groups will interact.</p>
72+
<p><img src="assets/images/docs/usermap.png" alt=""></p>
73+
<h3 id="AdminRolesAndGroups-ImportantNote">Important Note</h3>
74+
<p>A user can belong to any number of User Groups, but he can be assigned to only one Role. For example, if you want one of the Proofreader users to also be a Support document editor, you will have to create a different User for him to log in as, and assign that user to the Support user group.</p>
75+
<p>Remember, Roles assign permissions - WHAT the user can do. User groups assign WHICH DOCUMENTS the user can work with, but he can only do what the role he was assigned to allows.</p>
76+
<h3 id="AdminRolesAndGroups-Usergroups>Documentgroups">User groups-&gt;Document groups</h3>
77+
<p>Now we need to connect the user groups to the document groups we want them to have access to. For example, the Proofreaders user groups will be connected to ALL of the document groups, since his job will be to correct errors in all documents. The Marketing user group should have access to the Corporate and the Support document groups. And of course the Product user group should be connected to the Product document group.</p>
78+
<p><img src="assets/images/docs/access3.jpg" alt=""></p>
79+
<p>Now, as documents are created, they need to be assigned to the proper Document groups. As users are created, they are assigned to a certain Role, then to their proper User Groups. Only users belonging to user groups connected to a given document's document group can have access to that document. Even if a user has access to a given document, he can only do with it what his individial Role assignment allows.</p>
80+
<p>In this way, the Roles, User and Document Groups system allows a fine-grained control of individual document and admin user interaction.</p>

‎en/01_Info/01_Administration/10_Admin_Users/20_Reset_your_Password_-_Unblock_your_User.md‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
<p>We all have it happen at one point in time or another… We forgot our admin interface username/password, and then trying the different options we get blocked!</p>
2+
<h2>Database Editor to the Rescue</h2>
3+
<p>The secret to regaining access, your database editor, usually PHPMyAdmin granted other editors will work just fine.</p>
4+
<p>The first step is to open your database editor and browse to your Evo database.</p>
5+
<h3>Forgotten Password</h3>
6+
<ol>
7+
<li>
8+
<p>Open the <strong>(PREFIX)_manager_users</strong> table (where (PREFIX) is your table prefix)</p>
9+
</li>
10+
<li>
11+
<p>Edit the record for your username</p>
12+
</li>
13+
<li>
14+
<p>Change the password filed to: e10adc3949ba59abbe56e057f20f883e (Your password will be: 123456)</p>
15+
</li>
16+
<li>
17+
<p>Save the change</p>
18+
</li>
19+
<li>
20+
<p>If you aren't blocked attempt to login with the new password</p>
21+
</li>
22+
<li>
23+
<p>Change the password after you login!</p>
24+
<div class="note"><strong>Advanced Tip</strong><br>
25+
You can set any password by changing the drop down field type to MD5. Just enter the desired password instead of the above hash.</div>
26+
</li>
27+
</ol>
28+
<h3>Block Too</h3>
29+
<ol>
30+
<li>Open the <strong>(PREFIX)_user_attributes</strong> table (where (PREFIX) is your table prefix)</li>
31+
<li>Edit the record for your user (The admin user is typically id 1)</li>
32+
<li>Change the blocked column value from 1 to 0</li>
33+
<li>Save the change</li>
34+
<li>Attempt to login using your username and password (or newly set password from above)</li>
35+
</ol>
36+
<h2>Limited Access</h2>
37+
<p>In some cases you may not have access to a database editor readily available, in those cases it is still possible to restore admin interface access. You will need to upload your own database editor, such as <a target="_blank" rel="nofollow" href="//www.phpmyedit.org/">phmyedit</a>.</p>
38+
<p>You only need basic functionality, so a smaller editor will save you some time. Once uploaded you can copy the database information from the Evo config file (manager/includes/config.inc.php).</p>
39+
<p>This can be helpful should the client be abandon by their prior developer, their hosting company not provide access to a database editor, or you are in a pinch and only have FTP access.</p>
40+
<h2>Add a user via MySQL</h2>
41+
<p>It is possible to add a new admin user without going through the Admin Interface, if possible you should always use the admin interface.</p>
42+
<p>You will need to add two records to different tables, your database may not have the default prefix, if this is the case look for the same table name without the default prefix.</p>
43+
<ol>
44+
<li>Open the <strong>(PREFIX)_manager_users</strong> table</li>
45+
<li>Create a new record with the desired username and password (see forgot password for a hash to use)</li>
46+
<li>If you are able to run SQL commands you may optionally run:</li>
47+
</ol>
48+
<div><div id="highlighter_913734" class="syntaxhighlighter php"><div class="toolbar"><span><a href="#" class="toolbar_item command_help help">?</a></span></div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td class="gutter"><div class="line number1 index0 alt2">1</div></td><td class="code"><div class="container"><div class="line number1 index0 alt2"><code class="php plain">INSERT INTO manager_users (username,password) VALUES (</code><code class="php string">'yourname'</code><code class="php plain">,</code><code class="php string">'e10adc3949ba59abbe56e057f20f883e'</code><code class="php plain">);</code></div></div></td></tr></tbody></table></div></div>
49+
<ol>
50+
<li>After adding the user make note of the ID number for your user, you will need it in a moment.</li>
51+
<li>Open the <strong>(PREFIX)_user_attributes</strong> table</li>
52+
<li>Create a new record with an InternalKey of your user ID (the number you just forgot from before), and a role of 1</li>
53+
<li>If you are able to run SQL commands you may optionally run (substitute the 4 with your user id):</li>
54+
</ol>
55+
<div><div id="highlighter_989176" class="syntaxhighlighter php"><div class="toolbar"><span><a href="#" class="toolbar_item command_help help">?</a></span></div><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td class="gutter"><div class="line number1 index0 alt2">1</div></td><td class="code"><div class="container"><div class="line number1 index0 alt2"><code class="php plain">INSERT INTO user_attributes (InternalKey,role) VALUES (</code><code class="php string">'4'</code><code class="php plain">,</code><code class="php string">'1'</code><code class="php plain">);</code></div></div></td></tr></tbody></table></div></div>
56+
<p>Once you have created both records you should be able to login to the manager using the username and password set in step 2. Once logged in make sure to change your password!</p>

‎en/01_Info/01_Administration/10_Admin_Users/30_Why_Admin_Users,_Roles_and_Groups.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
<p>The primary reason for setting up admin users and groups is to be able to control access to the documents in the Document Tree. Admin interface users are stored separately from web (front-end) users for security reasons. A web user cannot log into the back-end nor can an Admin user log into the web site (front-end).</p>
2+
<p>Admin Roles are also used to control access to system management functions.</p>
3+
<p>Each admin user is assigned a Role that controls what permissions he is granted in areas of system and user administration and document management. An Admin user can only be assigned one Role.</p>
4+
<p>Admin users are assigned to one or more admin user groups:</p>
5+
<p>Both "Admin User Groups" and "Web User Groups" can be assigned to the same "Document Group."</p>

‎en/01_Info/01_Administration/10_Admin_Users/index.md‎

Whitespace-only changes.

‎en/01_Info/01_Administration/index.md‎

Whitespace-only changes.

0 commit comments

Comments
 (0)