ExpandOps

Access Code Lite lets you require a simple URL parameter code (e.g. ‘?access_code=enter123’) before visitors can view your site. 
Simply share the private access link (e.g. https://example.com?access_code=enter123) that the plugin generates to any user who you wish to grant access. 
Ideal for development, staging, previews, or private sharing without complex authentication.
Features: 
– Set a custom access code from the plugin settings page. 
– Code can be 3–12 characters, letters and numbers only. 
– Session persistence (default): visitors only need to enter the code once per visit. 
– Logged-in users, WordPress login, password reset, admin, AJAX, and cron are always allowed.
Important: Access Code Lite is not a security plugin. 
It does not encrypt, hide, or protect sensitive data. It only adds a simple URL parameter check and should be used for low-risk scenarios like development, staging, or preview access. 
Do not rely on this plugin to secure private or confidential information.
More persistence options (cookies, tokens, etc.) will be added in future versions.

Access Code Lite

Restrict site access with a simple URL code parameter and grant access using private link sharing. Ideal for sites in development or maintenance.

Scott Reilly

Though it is typically an individually configurable aspect of WordPress, there are times when forcing a single admin color scheme upon all users of a site can be warranted, such as to:
<ul>
<li>Provide a unique backend color scheme for multiple sites used by the same set of users to reinforce the difference between the sites.</li>
<li>Clearly denote backend differences between a production and staging/test instance of a site. Especially given that in this situation with the same plugins active and often the same data present, it can be easy to get mixed up about what site you’re actually on.</li>
<li>Force a site brand-appropriate color scheme.</li>
<li>Crush the expression of individuality under your iron fist.</li>
</ul>
Additionally, the plugin removes the “Admin Color Scheme” profile setting from users who don’t have the capability to set the admin color scheme globally since being able to set its value gives them the false impression that it may actually apply.
Links: <a href="https://coffee2code.com/wp-plugins/force-admin-color-scheme/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/force-admin-color-scheme/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/force-admin-color-scheme/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin is further customizable via one filter. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).
c2c_force_admin_color_scheme (filter)
The ‘c2c_force_admin_color_scheme’ filter allows you to set or override the forced admin color scheme. Use of the constant (“) takes priority over the filtered value, but the filtered value takes priority over the value set via the admin.
Arguments:
<ul>
<li>$color (string): The name of the admin color scheme. If an empty string is returned, then the plugin will behave as if no forced admin color scheme has been defined.</li>
</ul>
Example:
<pre><code>/**
 * Sets a forced admin color scheme based on user. Admins get one color scheme, whereas everyone else gets another.
 *
 * @param string $color The current forced admin color scheme. Empty string indicates no forced admin color scheme.
 * @return string
 */
function my_c2c_force_admin_color_scheme( $color ) {
 return current_user_can( 'manage_options' ) ? 'sunrise' : 'coffee';
}
add_filter( 'c2c_force_admin_color_scheme', 'my_c2c_force_admin_color_scheme' );
</code></pre>

Force Admin Color Scheme

Force a single admin color scheme for all users of the site.

Access Code Lite vs Force Admin Color Scheme