= Administrative web interface =

Each BOINC project has an '''administrative web interface''' that lets you

 * Browse the database
 * [ProfileScreen Screen user profiles]
 * Administer "special users" (e.g., forum moderators)
 * Create and edit applications and app versions
 * Send mass email to users (note: a more flexible way of doing this is described [VolunteerRecruit here]).
 * Send emails to users with malfunctioning hosts.
 * See a distribution of how many FLOPs results are using.
 * Cancel workunits
 * View recent results, and analyze failures
 * Browse stripcharts
 * Browse log files

If your project's URL is '''http://a.b.c/test''',
then the URL of the admin web interface is '''http://a.b.c/test_ops'''.
The directory containing the admin pages is '''~/projects/test/html/ops/'''.

Because the admin interface lets you do things like
see user email addresses, it's extremely important that it be secure.
There are two levels of protection:

== Protection by .htaccess ==

When a project is created, a file '''html/ops/.htaccess''' is created
that disallows access to the admin web interface.
You can use '''htpasswd''' to create a '''.htpasswd''' file containing
credentials for yourself.

== Project-defined protection policy ==

The project-specific config file '''html/project/project.inc'''
contains a function '''auth_ops()''' that defines
a project-specific policy for protecting the admin interface.
Possible policies:

 * No access (the default for new projects)
 * Access only if logged in as user from a given list.
 * Access only to users with ADMIN or DEV flag set in forum_preferences.privileges.
 * Any other policy you can think of.

By default, no access is allowed;
you'll need to edit this function to specify your project's policy.

Existing projects: look at '''html/project.sample/project.inc''',
copy the '''auto_ops()''' function into your project.inc file,
and edit it to specify your project's policy.