1. Dashboard
Definition:
The Dashboard module provides users with personalized dashboard pages similar to
iGoogle or MyYahoo. Users can add widgets to their pages and arrange them
through the use of a drag and drop interface. Administrators can create widgets
through the use of blocks and nodes defined within the system.
Design principals:
Keep the user’s context with inline customization. Avoid separate pages and never
use popups or lightboxes.
Actions should have instant results. Update the screen immediately and tell the
server in the background, no throbbers, spinners, or progress bars.
Status:
Functional and fully tested. Some notes about testing and functionality:
Cross browser compatible with all versions of IE, FF, Chrome, Safari, and Opera.
Heavily tested against Drupal.org’s new Bluecheese theme, along with other custom
themes.
Makes heavy use of preprocessing functions. After installing, be sure to clear your
theme registry. Refer to README.txt for instructions.
New Features in Dev 2.x:
fully functioning admin screens
one-click create widget from existing block
Multi-dashboard configuration
configurable dashboard default setup

2. Requirement Dashboard
Requirement Dashboard is an API module that allows you to define paths that can
behave the same way as admin/reports/status. These dashboards utilize the same
type of requirements specification that drupal natively provides via the
hook_requirements. By itself this module doesn't do anything but it does come
shipped with 2 submodules as example implementations of the API:
requirement_dashboard_og -- Dashboards that only show up for dashboards. Also
shows how you can use built in drupal hooks to extend the functionality of this api
and comes with some basic information rendered to the dashboard provided at
node/%/og_status
requirement_dashboard_system -- System wide dashboard. A good way of giving
out information about the site to non-admins that still potentially moderate content.
You can do two things with this API -- Create dashboards and define requirements to
show up on dashboards. Requirements can be added in from any module to allow
for other modules to supply their own useful data to dashboards.
All dashboards also have their own permission so that you can define different types
of dashboards for different roles, giving the users of your site the level of information
they should have access to for making better decisions (is the hope).
Example creation of a dashboard:
function hook_requirement_dashboard_provider() {
$dashboards['og'] = array(
'title' => 'Group Status',
'path' => 'node/%node/og_status',
);
return $dashboards;
}

3. UserDashboard
The User Dashboard module forks Drupal 7's awesome Dashboard module to
provide an individual dashboard for each user on the site.
Users can access their dashboards at the /user/dashboard (or /user/[uid]/dashboard)
page, and take advantage of the same drag & drop functionality as in the original
Dashboard module.
Administrators can configure which blocks can be used on the user dashboard via
the settings form at /admin/dashboard/user_dashboard/settings.
Release notes:
7.x-1.0
- initial release
7.x-1.0.1
- bug fixes
7.x-1.0.2
- bug fixes
7.x-1.0.3
- bug fixes
7.x-1.1
- added "default blocks" functionality to set the blocks initially shown for new users
7.x-1.1.1
- removed leftover debugging code
- added README.txt
- added permission handling for user dashboard pages
7.x-1.2
- identical to 7.x-1.1.1, but moved over to Drupal.org; bumped version number to
clearly differentiate between the two copies;
7.x-1.3
- Fix bug when moving blocks
- Add CSS to match the original dashboard layout

4. Working with the dashboard
Last updated March 16, 2012. Created by arianek on December 16, 2009.
Edited by jhodgdon, LeeHunter, Itangalo, Amazon. Log in to edit this page.
The dashboard gives administrators a customizable overview of important site
information. You can add and remove items from the dashboard, or you can disable
the dashboard completely.
Displaying the dashboard
On the admin toolbar click Dashboard or navigate
to http://www.example.com/admin/dashboardand you will see:
Adding, removing, or rearranging items in the dashboard
Click Customize Dashboard, and you will see a set of dashboard blocks that you can
drag and drop into and out of your personalized dashboard. Once dragged into the
dashboard, you can also rearrange each block into the desired position in the page.
(The settings are saved automatically.)

5. The finished dashboard blocks will fill with information as the site is populated with
content and users.
Disabling the dashboard
1. On the admin toolbar, navigate to the Modules administration page (Administer >
Modules or http://example.com/admin/modules).
2. In the Core section, disable the Dashboard module.
3. Click "Save Configuration".
Dashboard Views
A collection of preconfigured Views to add to the dashboard of your Open Atrium
groups.
Currently includes:
Book pages (with "Add Book page" link)
Member Listing (including admin vs. user status)
Projects (Case Tracker or Case Tracker Plus)
Shoutbox
Additional submissions are welcomed.
Installation
1. Visit /admin/build/features on your site to enable this Feature.
2. Visit /admin/settings/dashboard on your site, select the "Dashboard Views" section,
and enable this module's blocks.

6. Activity Dashboard
This module generates a site "dashboard" type feature that can enable site admins
to see some top level statistics for their Drupal site illustrated with visually appealing
charts, created with a Silverlight library. It is an API only module and is designed to
be extended by other developers using a couple of simple hooks. In this very early
version, it has the following features:
A configuration page for setting chart options and styles
A dashboard overview page to display different types of data
Individual dashboard pages rendering any number of charts, either as bar or pie
charts
A developer API to allow modules to create dashboard pages
An example module to demonstrate the API
Administration Dashboard
This module will provide a sort of control panel for users with administrative rights. It
can be used to store commonly used links or to add block content to the 'dashboard'
region.
On installation of the module, a Dashboard menu is created in the menu system. The
menu is configurable, just like other menu's.
After installation you can configure the Dashboard by either assigning blocks to it's
region or by changing the menu structure on admin/build/menu-
customize/dashboard, or by navigating to the Dashboard Settings page.
By clicking the 'Toggle default visiblity'-button (the little green one) you can tell the
Dashboard whether the Dashboard must remember it's last state (shown or hidden)
for after a page-refresh. If this is disabled, the Dashboard is always hidden after a
page-refresh.
In the permission table you can set the permissions for using an configuring the
Dashboard.
It would be really nice letting the Dashboard be user dependent. This way all
privileged users can change the Dashboard to their needs. Then the dashboard
settings should be reachable from a tab next to the user settings.

7. Drupal Remote Dashboard
This module is for system administrators. It's a tool to monitor and manage any
number of Drupal installations at once and it's built to be extensible by other
modules. Since version 2.X this module also comes with the highest level of security
where as all communication between the dashboard and each of the cores is AES
encrypted, hence the dependency (see below). Optionally the monitoring data will be
made visible in nice graphs if the Google Chart API is available.
Features
Dashboard: It consists of filterable lists of Cores or Domains including a lot of
detailed information about each of them and also an extensible list of actions that
can be performed on selected cores or domains. The dashboard is only available for
Drupal 7.
Monitoring: With all these information coming on from the Cores and Domains, we
can monitor our platforms and configure specific checks.
Remote actions: To update information or to do maintenance on our Cores and
Domains we can execute remote actions. Clear cache or run cron on any specific
number of Domains.
How it works
When installing DRD and adding a core to the dashboard by providing one of the
domains of that core, the dashboard adds that core entity to the database and
performs the following actions:
Run a script on the remote core to install the module drd_server for the given domain
Send the encryption settings from DRD to the remote core. To be able to do this, you
have to insert the IP address of the DRD Server to the settings of “drd_server”
module on your remote core. A link to get there directly is provided in DRD
After that, DRD is reading all available domains from the remote core and updates
the encryption keys for each of the domains
Then, DRD is reading all available actions from the remote core and domain
This is repeated for each new Core you're adding to your dashboard. That provides
you with a list of all Cores including a lot of additional information, i.e. the number of
hosted domains on each Core. You can now always switch between the Cores
overview and the domain list. In both of those lists you can always select one or
more items and then select one of the available actions from the drop-down above
the list to execute.
Roadmap
Here is what we're planning for the next few release:
Monitoring and alerts
Supporting logs on the remote cores and domains
Provide sample modules to demonstrate extensibility and the API
Start support for Drush, i.e. allow to update modules from within DRD by using Drush
over ssh
Query remote databases

8. Total Control Admin Dashboard
What is Total Control?
The Total Control Admin Dashboard creates a default panel page with useful
administration tools. Its purpose is to create a central location from which a Drupal
site can be properly cared for. Several overview panes are included for site stats and
quick reference. Several administration panes are provided with quick links to
content types, menus, taxonomy, and other scattered locations of important Drupal
site administration. Several views panes are also provided as well as full-page
comprehensive versions of the views with bulk operations. Each views panel pane is
customizable via it's pane settings, or override the default views provided to suit your
own needs.
Why another admin dashboard module?
I evaluated all the other admin dashboards out there and realized that none of them
seemed to do much more than take the pre-existing Drupal admin area and display it
differently. The Dashboard module in drupal core doesn't actually add anything
useful, and is an abomination of the arcane blocks system. This module provides a
useful alternative.
Panels Content Panes Included:
create content: list of 'add' links for each content type
content overview: number of posts in each type, comment count, spam count
user overview: total number, active and blocked counts, and role counts
site overview: combination of user and content overviews, above.
taxonomy: administrative list of all vocabularies on your site
menus: administrative list of all menus on your site
content types: administrative list of all content types on your site
panels: administrative list of all active panels on your site
webforms: administrative list of all webforms on your site
nodequeue: administrative list of all nodequeues on your site
Views Included:
all content (both panel pane and page)
content by type (both panel panes and pages for every type on your site)
all users (both panel pane and page)
users by role (both panel pane and page for every role on your site)
comments (both panel pane and page)
categories (both panel pane and page)
activity (both panel pane and page)
files (both panel pane and page)