GetSimple CMS Roles & Permissions | OpsBlu Docs

GetSimple CMS Roles & Permissions

GetSimple CMS single-admin model -- file-based user management and template access for analytics.

GetSimple CMS is an ultra-lightweight flat-file CMS designed for simplicity. It has a minimal permission model focused on a single administrator.

Permission Model

GetSimple uses a single-user admin model by default. The Multi-User plugin extends this to support multiple users with limited roles.

Default (Single User)

Access Level Full Admin
Edit pages Yes
Edit theme Yes
Manage plugins Yes
Upload files Yes
Site settings Yes

With Multi-User Plugin

Role Edit Pages Edit Theme Manage Plugins Upload Files Settings
Admin Yes Yes Yes Yes Yes
Editor Yes No No Yes No

Analytics Integration

Only the admin can edit theme templates where analytics scripts are placed:

<?php // Edit: theme/YOUR_THEME/template.php ?>
<?php // Add before </head> ?>
<head>
  <?php get_header(); ?>
  <script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
  <script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());
    gtag('config', 'G-XXXXXXXXXX');
  </script>
</head>

User Storage

Users are stored as XML files in data/other/:

<!-- data/other/user.xml -->
<item>
  <USR>admin</USR>
  <PWD>$2y$10$hashedpassword...</PWD>
  <EMAIL>admin@example.com</EMAIL>
  <HTMLEDITOR>1</HTMLEDITOR>
  <TIMEZONE>America/New_York</TIMEZONE>
  <LANG>en_US</LANG>
</item>

Custom Roles

GetSimple does not support custom roles natively. The Multi-User plugin adds basic Editor support. For more granular permissions, consider migrating to a more feature-rich CMS.

Best Practices

  1. Secure the admin panel with .htaccess IP restrictions since GetSimple has no built-in 2FA
  2. Keep GetSimple and all plugins updated -- the flat-file architecture means compromised admin access exposes all files
  3. Use the Components plugin to store analytics code as a reusable component
  4. Back up the data/ directory before making configuration changes
  5. If using Multi-User plugin, restrict Editor accounts to content-only operations
Back to top