acces control methods, security policies are essentailly rules which dictate how certain services, software or hardware are made avaialble of denied to users.
usually the system administrator will allocate users to user groups, and allocate resources and services to user groups. a well structured security policy should allow authorised users access to whatever they need, and deny access to unauthorised users
some resources are allocated to specific users (for instance most *nix system allocate a certain amount of personal user space
on a *nix system you may have a webserver, in order to secure the system the userid the webserver uses should have minimum access rights to do things
in a dataabse server
you would have differnet levels and types of user
you might have system administrtators such as DBA's whcih can do things with tables, but can't view data
you could have developers who can look at the development server but are not allowed access to the live server
a specific userid or more likely usergroup might have access to specific tables or view and may have read only permission, may have read/write permissions or may have full data access and NO design access.
whatever else you do do, you should rarely run software when in adminstrator mode... that is one of the biggest vulnerabilities in Microsoft systems in as much as most users use the default user id with admin permissions, when they shoudk reserve admistrator for occasional use, and use other accounts as required.