How to block customer access to my WPMU Dev Dashboard

Both my customers and I are WP Administrators. I want them to have full access to the video tutorials; however, how do I block them from seeing my WPMU Dashboard?

  • Mike Macey

    Shreyans , thank you for your response. I have downloaded the User Role Editor. Customer means the person I built their WordPress site for. I don't want them to have access to my WPMU dashboard inside their WordPress dashboard. I am always an Administrator with my clients.

    Aristath, should I include ' ' before and after my ID# ? Will adding this code to my wp-config.php file block my WordPress customer from accessing my WPMU dashboard from within their WordPress dashboard?

  • Mike Macey

    Ari, I see my API membership number. Where do I find my ID#?

    I am in my wp-config.php file but not sure where to insert the code you gave me:

    * The base configurations of the WordPress.
    * This file has the following configurations: MySQL settings, Table Prefix,
    * Secret Keys, WordPress Language, and ABSPATH. You can find more information by
    * visiting {@link Editing
    * wp-config.php} Codex page. You can get the MySQL settings from your web host.
    * This file is used by the wp-config.php creation script during the
    * installation. You don't have to use the web site, you can just copy this file
    * to "wp-config.php" and fill in the values.
    * @package WordPress

    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define('WP_CACHE', true); //Added by WP-Cache Manager
    define( 'WPCACHEHOME', '/home/newport1/public_html/' ); //Added by WP-Cache Manager
    define('DB_NAME', 'newport1_wpthinkupnewmedia');

    /** MySQL database username */
    define('DB_USER', 'newport1_wpusrth');

    /** MySQL database password */
    define('DB_PASSWORD', 'yeXW3wbBd19P');

    /** MySQL hostname */
    define('DB_HOST', 'localhost');

    /** Database Charset to use in creating database tables. */
    define('DB_CHARSET', 'utf8');

    /** The Database Collate type. Don't change this if in doubt. */
    define('DB_COLLATE', '');

    * Authentication Unique Keys.
    * Change these to different unique phrases!
    * You can generate these using the {@link secret-key service}
    * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
    * @since 2.6.0
    define('AUTH_KEY', 'put your unique phrase here');
    define('SECURE_AUTH_KEY', 'put your unique phrase here');
    define('LOGGED_IN_KEY', 'put your unique phrase here');
    define('NONCE_KEY', 'put your unique phrase here');

    * WordPress Database Table prefix.
    * You can have multiple installations in one database if you give each a unique
    * prefix. Only numbers, letters, and underscores please!
    $table_prefix = 'wp_';

    * WordPress Localized Language, defaults to English.
    * Change this to localize WordPress. A corresponding MO file for the chosen
    * language must be installed to wp-content/languages. For example, install
    * to wp-content/languages and set WPLANG to 'de' to enable German
    * language support.
    define ('WPLANG', '');

    /* That's all, stop editing! Happy blogging. */

    /** WordPress absolute path to the Wordpress directory. */
    if ( !defined('ABSPATH') )
    define('ABSPATH', dirname(__FILE__) . '/');

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . 'wp-settings.php');

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.