diff options
| -rw-r--r-- | gnome-help/C/user-admin-change.page | 49 | ||||
| -rw-r--r-- | gnome-help/C/user-admin-explain.page | 37 | ||||
| -rw-r--r-- | gnome-help/C/user-admin-privdescriptions.page | 24 | ||||
| -rw-r--r-- | gnome-help/C/user-admin-problems.page | 31 | ||||
| -rw-r--r-- | gnome-help/C/user-admin-restrictothers.page | 24 |
5 files changed, 95 insertions, 70 deletions
diff --git a/gnome-help/C/user-admin-change.page b/gnome-help/C/user-admin-change.page index c295434..9e3a3b9 100644 --- a/gnome-help/C/user-admin-change.page +++ b/gnome-help/C/user-admin-change.page @@ -3,9 +3,12 @@ id="user-admin-change"> <info> + <link type="guide" xref="user-privileges"/> - <desc>XXX</desc> - <revision pkgversion="3.0" version="0.1" date="2010-10-31" status="stub"/> + <link type="seealso" xref="user-admin-explain" /> + + <desc>You can change which users are allowed to make changes to the system by giving them administrative privileges.</desc> + <revision pkgversion="3.0" version="0.1" date="2011-03-20" status="review"/> <credit type="author"> <name>GNOME Documentation Project</name> <email>gnome-doc-list@gnome.org</email> @@ -14,8 +17,46 @@ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> </info> - <title>Change who has administrative privileges</title> - +<title>Change who has administrative privileges</title> + +<p>Administrative privileges are a way of deciding who can make changes to important parts of the system. You can change which users have admin privileges and which ones don't. They are a good way of keeping your system secure and preventing potentially damaging unauthorized changes.</p> + +<steps> + <item> + <p>Click your name on the top bar, select <gui>System Settings</gui> and open <gui>User Accounts</gui>.</p> + </item> + + <item> + <p>Click <gui>Unlock</gui> and enter your password to unlock the account settings. (To give a user admin privileges, you must have admin privileges yourself.)</p> + </item> + + <item> + <p>Select the user whose privileges you want to change and then click the option next to <gui>Account type</gui>.</p> + </item> + + <!-- FIXME: Check that the definitions below are correct! --> + <item> + <list> + <item> + <p>Choose <gui>Administrator</gui> if you want the user to be able to perform administrative tasks, like installing new applications.</p> + </item> + <item> + <p>Choose <gui>Standard</gui> if you don't want the user to be able to perform admin tasks.</p> + </item> + <item> + <p>Choose <gui>Supervised</gui> if you want the user to have an extra-secure user account which has extra restrictions on things like connecting to networks. Use this option if the user is someone you don't know (e.g. a "guest user"), or who may try to make unwanted changes to the system.</p> + </item> + </list> + </item> + + <item> + <p>Close the User Accounts window. The user's privileges will be changed when they next log in.</p> +</steps> + +<note> + <p>The first user account on the system is usually the one that has admin privileges. This is the user account that was created when you first installed the system.</p> +</note> + <comment> <cite date="2010-10-31" href="mailto:gnome-doc-list@gnome.org">GNOME Documentation Project</cite> <p>Explain how admin privileges can be given to other people, or removed. Warn the reader about how it's unwise to have too many admins on a system.</p> diff --git a/gnome-help/C/user-admin-explain.page b/gnome-help/C/user-admin-explain.page index d0785cc..89f6af0 100644 --- a/gnome-help/C/user-admin-explain.page +++ b/gnome-help/C/user-admin-explain.page @@ -4,8 +4,10 @@ <info> <link type="guide" xref="user-privileges"/> - <desc>XXX</desc> - <revision pkgversion="3.0" version="0.1" date="2010-03-19" status="stub"/> + + <desc>You need admin privileges to change important parts fo your system.</desc> + + <revision pkgversion="3.0" version="0.1" date="2010-03-20" status="review"/> <credit type="author"> <name>GNOME Documentation Project</name> <email>gnome-doc-list@gnome.org</email> @@ -14,11 +16,28 @@ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> </info> - <title>How do administrative privileges work?</title> - - <comment> - <cite date="2010-10-31" href="mailto:gnome-doc-list@gnome.org">GNOME Documentation Project</cite> - <p>Explain how admin privileges work. Pitch at a basic level. Explain why they are necessary, and how they promote security.</p> - </comment> - +<title>How do administrative privileges work?</title> + +<p>As well as the files that <em>you</em> create, your computer also has a number of files which are needed by the system for it to work properly. If these important <em>system files</em> are changed improperly they can cause various things to break, so they are protected from changes by default. Certain applications also modify important parts of the system, and so are also protected.</p> + +<p>The way that they are protected is by only allowing users with <em>administrative privileges</em> to change the files or use the applications. In day-to-day use, you won't need to change any system files or use these applications, so by default you do not have admin privileges.</p> + +<p>Sometimes you need to use these applications, so you can temporarily get admin privileges to allow you to make the changes. If an application needs admin privileges, it will ask for your password. For example, if you want to install some new software, the software installer (package manager) will ask for your admin password so it can add the new application to the system. Once it has finished, your admin privileges will be taken away again.</p> + +<p>Admin privileges are associated with your user account. Some users are allowed to have admin privileges and some are not. If you aren't allowed any admin privileges, you will not be able to install software, for example. Some user accounts (for example, the "root" account) have permanent admin privileges. You shouldn't use admin privileges all of the time, because you might accidentally change an important file and break something.</p> + +<p>In summary, admin privileges allow you to change important parts of your system when you need to, but prevent you from doing it accidentally.</p> + +<note> + <title>What does "super user" mean?</title> + <p>A user with admin privileges is sometimes called a <em>super user</em>. This is simply because that user has more privileges than normal users. You might see people discussing things like <cmd>su</cmd> and <cmd>sudo</cmd>; these are programs for temporarily giving you "super user" (admin) privileges.</p> +</note> + +<section id="advantages"> + <title>Why are admin privileges useful?</title> + <p>Requiring users to have admin privileges before important system changes are made is useful because it helps to prevent your system from being broken, intentionally or unintentionally.</p> + <p>If you had admin privileges all of the time, you might accidentally change an important file, or run an application which changes something important by mistake. Only getting admin privileges temporarily, when you need them, reduces the risk of these mistakes happening.</p> + <p>Only certain, trusted users should be allowed to have admin privileges. This prevents other users from messing with the computer and doing things like uninstalling applications that you need, installing applications that you don't want, or changing important files. This is useful from a security standpoint.</p> +</section> + </page> diff --git a/gnome-help/C/user-admin-privdescriptions.page b/gnome-help/C/user-admin-privdescriptions.page deleted file mode 100644 index 60110e4..0000000 --- a/gnome-help/C/user-admin-privdescriptions.page +++ /dev/null @@ -1,24 +0,0 @@ -<page xmlns="http://projectmallard.org/1.0/" - type="topic" style="tip" - id="user-admin-privdescriptions"> - - <info> - <link type="guide" xref="user-privileges"/> - <desc>XXXXX</desc> - <revision pkgversion="3.0" version="0.1" date="2010-03-19" status="stub"/> - <credit type="author"> - <name>GNOME Documentation Project</name> - <email>gnome-doc-list@gnome.org</email> - </credit> - - <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> - </info> - - <title>Description of the user privilege options</title> - - <comment> - <cite date="2010-10-31" href="mailto:gnome-doc-list@gnome.org">GNOME Documentation Project</cite> - <p>Moderately advanced topic. Describe what each of the user privilege options in the users-admin tool does. Can be technical if you like (e.g. "takes write permission away from /dev/whatever when enabled". Mention relevant gconf keys - this will be useful to system admins.</p> - </comment> - -</page>
\ No newline at end of file diff --git a/gnome-help/C/user-admin-problems.page b/gnome-help/C/user-admin-problems.page index fe04681..db36807 100644 --- a/gnome-help/C/user-admin-problems.page +++ b/gnome-help/C/user-admin-problems.page @@ -4,8 +4,10 @@ <info> <link type="guide" xref="user-privileges"/> - <desc>XXX</desc> - <revision pkgversion="3.0" version="0.1" date="2011-03-19" status="stub"/> + + <desc>You can only do some things, like installing applications, if you have admin privileges.</desc> + + <revision pkgversion="3.0" version="0.1" date="2011-03-20" status="review"/> <credit type="author"> <name>GNOME Documentation Project</name> <email>gnome-doc-list@gnome.org</email> @@ -14,11 +16,22 @@ <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> </info> - <title>Problems caused by administrative restrictions</title> - - <comment> - <cite date="2010-10-31" href="mailto:gnome-doc-list@gnome.org">GNOME Documentation Project</cite> - <p>Mention a few problems that might be caused by administrative restrictions, e.g. not being able to connect to a network or mount a disk. Point at topics explaining how to get around the problems, if possible.</p> - </comment> - +<title>Problems caused by administrative restrictions</title> + +<p>There are a few problems that you might experience because you don't have <link xref="user-admin-explain">administrative privileges</link>. Some things require you to have admin privileges in order to work, such as:</p> + +<list> + <item> + <p>Connecting to some networks/wireless networks</p> + </item> + <item> + <p>Viewing the contents of a removable disk plugged-in to the computer, or the contents of a different disk partition (e.g. if you have a Windows partition)</p> + </item> + <item> + <p>Installing new applications</p> + </item> +</list> + +<p>You can <link xref="user-admin-change">change who has admin privileges</link>.</p> + </page> diff --git a/gnome-help/C/user-admin-restrictothers.page b/gnome-help/C/user-admin-restrictothers.page deleted file mode 100644 index 850005d..0000000 --- a/gnome-help/C/user-admin-restrictothers.page +++ /dev/null @@ -1,24 +0,0 @@ -<page xmlns="http://projectmallard.org/1.0/" - type="topic" style="task" - id="user-admin-restrictothers"> - - <info> - <link type="guide" xref="user-privileges"/> - <desc>Lock down the computer by stopping others from accessing external disks, changing system settings, installing software, or connecting to other networks.</desc> - <revision pkgversion="3.0" version="0.1" date="2011-03-19" status="stub"/> - <credit type="author"> - <name>GNOME Documentation Project</name> - <email>gnome-doc-list@gnome.org</email> - </credit> - - <include href="legal.xml" xmlns="http://www.w3.org/2001/XInclude"/> - </info> - - <title>Restrict other users from performing certain actions</title> - - <comment> - <cite date="2010-10-31" href="mailto:gnome-doc-list@gnome.org">GNOME Documentation Project</cite> - <p>Explain how the user privileges tab in the users-admin tool can be used to restrict other users from accessing certain devices/features. Explain why this might be useful.</p> - </comment> - -</page> |