Site Configuration is about how the site behaves rather than what content it stores. As a Drupal site builder, most of your daily work happens in configuration screens: setting rules, defaults, permissions, and system behavior.
This topic focuses on understanding where settings live, what they affect, and how to manage them safely across environments.
What Site Configuration means in Drupal
Site configuration controls:
- How users interact with the site
- How content is created and managed
- How the system behaves behind the scenes
- How settings move between environments
Key idea:
Configuration defines site behavior and is exportable.
4.1 Core site configuration areas
Drupal groups configuration into logical sections under Configuration in the admin UI.
Account settings
Account settings control how users register and log in.
You can configure:
- Who can register (admins only or visitors)
- Email verification requirements
- Password policies
- Username and email behavior
Real example:
- Public site → users can register, email verification required
- Internal site → only administrators create accounts
Content authoring settings
These settings affect how content is created.
You can configure:
- Default publishing options (published/unpublished)
- Preview before submitting
- Revision behavior
- Content moderation (if enabled)
Real example:
- News content defaults to unpublished
- Editors review content before publishing
Development settings
Development settings are mainly used by administrators.
You may configure:
- Error message visibility
- Logging and error reporting
- Performance-related settings
Rule:
Detailed errors should never be shown on production sites
Search settings
Search configuration controls how users find content.
You can configure:
- Which search modules are enabled
- Indexing behavior
- Search permissions
Real example:
- Enable search for authenticated users only
- Exclude certain content types from search
Site & system settings
These settings define site-wide behavior.
Common settings include:
- Site name and slogan
- Front page path
- Error pages (403 / 404)
- File system settings
- Date and time formats
These settings affect the entire site experience.
Media settings
Media configuration controls how files and media behave.
You can configure:
- Media types
- Allowed file types
- Image styles
- Media library behavior
Real example:
- Limit uploads to specific image formats
- Control image sizes using image styles
4.2 Configuration Management (Import / Export)
Drupal separates configuration from content so settings can move between environments.
What configuration management does
It allows you to:
- Export site configuration
- Import configuration into another environment
- Compare configuration differences
This ensures:
- Consistency between environments
- Predictable deployments
- Fewer manual mistakes
What is configuration
Examples of configuration:
- Content types
- Fields
- Views
- Roles and permissions
- Site settings
Examples of non-configuration:
- Nodes
- Comments
- Media items
Real workflow example
Typical workflow:
- Make configuration changes on Dev
- Export configuration
- Import configuration on Test or Prod
Rule:
Never manually recreate configuration on production
4.3 User accounts and roles
User configuration controls who can do what on the site.
Users
A user account represents a person accessing the site.
User settings include:
- Status (active/blocked)
- Roles assigned
- Language preference
Roles
Roles group permissions.
Common roles:
- Anonymous
- Authenticated
- Editor
- Administrator
Permissions are assigned to roles, not individual users.
Permissions
Permissions control actions users can perform.
Examples:
- Create content
- Edit own content
- Administer site configuration
Real example:
- Editors can edit content but cannot change site settings
- Administrators can manage configuration
Rule:
Grant the least permissions necessary
Common site builder mistakes
- Editing configuration directly on production
- Giving editors administrative permissions
- Forgetting configuration export/import
- Showing error messages to end users
Summary: Site Configuration the Drupal way
Site Configuration defines how a Drupal site behaves. Account settings control users, content authoring settings control workflows, system settings affect the entire site, and configuration management ensures consistency across environments. User roles and permissions should always be carefully planned to balance flexibility and security.
Strong site configuration leads to stable, secure, and maintainable Drupal sites.