Adding & Removing Users on Blogger

Blogger uses Google Account-based permissions tied to each blog. There are no standalone user accounts -- every collaborator must have a Google Account, and access is granted per-blog through the Blogger dashboard or the Blogger API v3.

Adding Users via the Blogger Dashboard

Inviting Authors and Admins

1. Open blogger.com and select the target blog
2. Navigate to Settings in the left sidebar
3. Scroll to the Permissions section
4. Under Blog authors, click Add authors
5. Enter one or more email addresses (comma-separated)
6. Click Invite authors

Invited users receive an email with a link to accept. Until they accept, they appear as "Invited" in the permissions list. Once accepted, they default to the Author role.

Promoting Users to Admin

1. In Settings > Permissions > Blog authors, find the user
2. Click the dropdown next to their name
3. Select Admin

Admin users can manage all posts, change blog settings, add or remove other users, and delete the blog itself. Blogger supports only two roles: Author (create and edit own posts) and Admin (full control).

Adding Users via the Blogger API v3

The Blogger API does not expose a direct "invite user" endpoint. Blog membership is managed through the dashboard. However, you can programmatically list current users and their roles:

# List all users for a blog using the Blogger API v3
curl -s \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  "https://www.googleapis.com/blogger/v3/blogs/BLOG_ID/users/self"

# Retrieve blog details including author info
curl -s \
  -H "Authorization: Bearer $(gcloud auth print-access-token)" \
  "https://www.googleapis.com/blogger/v3/blogs/BLOG_ID?fetchUserInfo=true"

For automation, use the Google Admin SDK (Google Workspace only) to manage Google Account access at the organizational level, then grant Blogger permissions through the dashboard.

Removing Users

Removing Authors and Admins

1. Go to Settings > Permissions > Blog authors
2. Click the X icon next to the user you want to remove
3. Confirm the removal

What Happens to Their Content

When you remove a user from a Blogger blog:

• Posts they authored remain published on the blog
• Posts show the original author name but link to a "Profile Not Available" page
• Draft posts are preserved and become accessible to admins
• The removed user loses all access immediately -- no grace period
• If you want to reassign authorship, you must manually edit each post (Blogger does not support bulk author reassignment)

Revoking Your Own Access

A user can leave a blog voluntarily:

1. Go to blogger.com
2. Click the blog name
3. Go to Settings > Permissions
4. Click Leave this blog next to your own name

The last remaining admin cannot leave -- you must transfer admin to another user first.

Bulk User Management

Blogger has no built-in bulk user management. For Google Workspace organizations managing many blogs:

# Use Google Workspace Admin SDK to list all users in the org
# Then cross-reference with Blogger permissions per blog

# List org users via gcloud
gcloud identity groups memberships list \
  --group-email="bloggers@yourdomain.com" \
  --format="table(preferredMemberKey.id, roles.name)"

# Export blog author list (scrape from Settings page or use API)
curl -s \
  -H "Authorization: Bearer $TOKEN" \
  "https://www.googleapis.com/blogger/v3/blogs/BLOG_ID" \
  | jq '.posts.totalItems, .pages.totalItems'

For organizations with 10+ blogs, consider creating a Google Group and managing membership at the group level. Blogger does not natively support group-based access, but you can standardize your invite process by maintaining a group roster.

Google Workspace SSO Integration

Blogger inherits authentication from Google Accounts. If your organization uses Google Workspace:

• SSO is automatic -- users sign in with their Workspace credentials
• 2FA enforcement applies from Google Workspace admin settings
• Session management is controlled at the Workspace level (Admin Console > Security > Google session control)
• When you suspend a Google Workspace account, the user immediately loses access to all Blogger blogs
• When you delete a Google Workspace account, their Blogger posts remain but authorship shows as unavailable

Enforcing Access Policies

Google Workspace Admin Console path:
Admin Console > Apps > Additional Google services > Blogger

Options:
- ON for everyone (default)
- OFF for everyone
- ON for specific organizational units

Disabling Blogger at the OU level prevents users in that unit from creating new blogs or accepting blog invitations, but does not remove them from blogs they already belong to.

Offboarding Checklist

When removing a team member from Blogger:

1. Reassign critical posts -- Edit posts to update author if needed for branding
2. Download their drafts -- Export any unpublished drafts before removal (Settings > Other > Back up content)
3. Remove from all blogs -- Check every blog in the organization, not just the primary one
4. Revoke Google Account access -- If using Workspace, suspend or delete the account
5. Update blog contact info -- If the removed user's email appears in the blog's About page or contact form
6. Check connected services -- Remove their access from associated GA4 properties, Google Search Console, and AdSense accounts

Troubleshooting Common Issues