This guide explains the Blog Manager features available to elevated website users. In this module, Site Admins, users in the website Administrators role, and users in the Upendo Client role use the same elevated Blog Manager permissions. A site may still apply normal website page and module permissions before Blog Manager opens.
Your elevated access
An elevated user can manage all blog posts for a website that the user is allowed to access. You can:
- Create, edit, publish, schedule, archive, and delete any blog post.
- Choose or change the author when the form allows it.
- Create categories and tags.
- Open the Blog Manager settings.
- Choose which website roles may publish their own posts.
- Run SEO maintenance.
- Remove unused categories and tags.
- Permanently remove soft-deleted posts.
- Import live blog content when the import feature is installed and available.
The server checks each action. Seeing a button does not replace server permission checks.
What website visitors see
Visitors see only posts that are public for the selected website. Drafts, future scheduled posts, and deleted posts are not shown as normal public articles. Changes to a post can change its title, address, images, search text, social sharing text, and whether the post appears in public lists.
Choose a website
The website selector appears when your account can work with more than one website. Select a website before creating or changing content. Categories, tags, authors, roles, files, posts, and settings belong to the selected website.
Do not assume that a category or role from one website is available on another website. Change the website first, then review the available choices.
Manage posts
Use the post list to search and filter by text, status, category, or scheduled state. Open a post to edit it, or select New Blog Post to create one.
When managing another person's post, check the following before saving:
- The selected website is correct.
- The author is correct.
- The status is correct.
- The publish start and end dates are correct.
- The category and tags match the article.
- The title, slug, images, and SEO fields are correct.
Changing a slug changes the article address. Blog Manager keeps a history of changed slugs so older addresses can continue to be handled when the site's routing supports it. Still, treat a slug change as a public change and check the article after saving.
Elevated users can create a category or tag while editing a post. Use short, clear names and follow the site's naming rules. Before adding a new value, search the existing list so you do not create a duplicate.
Categories and tags affect filters, navigation, and search. A poor naming choice can make it harder for visitors to find related articles.
Configure Blog Publisher Roles
Blog Publisher Roles are website-level settings. Users in the selected roles can create and manage their own posts, but they cannot create categories or tags and cannot manage every post.
- Open the Blog Manager post list.
- Select Settings.
- In Blog Publisher Roles, select one or more active website roles.
- Save the settings.
Select only roles that should be trusted to write and publish content. The setting uses the selected website's roles. A role with the same name on another website does not automatically receive access there.
After you change the setting, ask a test user in the selected role to sign in and verify the expected access. Also test a user who is not in the role to make sure access is not broader than intended.
Backfill missing SEO data
The settings window can include Backfill missing SEO data. This fills missing social sharing titles, social sharing descriptions, and answer-friendly summaries for posts on the selected website.
The process uses SEO title and SEO description values already saved on each post. It does not change posts on another website. Review the results after the process finishes. Generated text is a starting point, not a replacement for a careful human review.
The settings window may include cleanup choices for unused categories and tags. Use them only after checking the list and confirming that the values are not needed for future content.
Removing an unused value can change filters and old management workflows. The cleanup action is intended for values that are not assigned to any blog post.
Permanently delete soft-deleted posts
Deleting a post from the list normally performs a soft delete first. The settings window may include Permanently Delete Soft-Deleted Blog Posts.
This is permanent. It can also remove related comments, tag assignments, and import tracking records. Confirm that backups and retention needs are satisfied before running it. Do not use this option as a normal way to hide a post; use the post status or soft delete instead.
Import blog content
If the import feature is installed and configured, an elevated user can select Import. Read the import preview and warnings before starting. Check titles, authors, slugs, images, links, and duplicate information. Imported content should be reviewed as draft content before it is made public.
If import is unavailable, the required importer may not be installed, the live blog tables may not exist, or your deployment may not include this feature.
Security and content checks
- Use the correct website before every change.
- Do not give Blog Publisher access to a broad role unless every member should be able to create posts.
- Review HTML content before publishing it.
- Use meaningful image alternative text.
- Avoid putting private information in titles, summaries, images, or SEO fields.
- Confirm that a delete or cleanup action is intended before confirming it.
Troubleshooting
Settings is missing
Your account may not be elevated, the module may not be installed on the current page, or normal website permissions may block the action.
A user still cannot create a post
Check that the user belongs to a selected Blog Publisher Role on the same website. Then ask the user to sign out and sign in again if the site caches role membership.
A post is not public after saving
Check the post status, publish start date, publish end date, website, and any page or viewer settings. A saved post is not always a public post.
Elevated-user checklist
- I selected the correct website.
- I gave publishing access only to the intended roles.
- I reviewed the post status and dates.
- I checked the public article after important changes.
- I treated permanent cleanup as an irreversible action.