Overview

In Khoros Community (Aurora), users with a custom role that includes "Edit all events" may be unable to publish edits to events created by other members. Clicking Publish does not save the changes; instead, the editor displays an "Autosave Recovered" toast message and the event remains unmodified.

This happens because the publish payload includes the event's tag data. Even though the role has event-editing permissions, the platform separately enforces tag permissions when the event contains tags. If the role lacks "Add tags to any post", the entire publish action is rejected server-side.

In This Article

• Symptoms
• Root Cause
• Resolution
• Quick Diagnostic Test
• Additional Information
• FAQ

Symptoms

• Users in a custom role (e.g., "EventManager") click Publish after editing an existing event but the save does not complete.
• A toast notification reading "Autosave Recovered" appears at the top of the event editor.
• The issue affects all users in the same role, not just a single account.
• The issue only occurs when editing events created by other users that contain one or more tags.
• Clearing browser cache/cookies and testing in Incognito mode does not resolve the problem.
• The browser console shows a GraphQL error for the updateOccasion operation with classification DataFetchingException.

Root Cause

When a user clicks Publish, the Aurora editor sends a GraphQL UpdateOccasion mutation that includes all event fields — including the tags array. The backend validates tag permissions independently of event-editing permissions.

If the event was created by another user and contains tags, the platform requires one of the following permissions on the role:

• Add tags to any post (allow_add_labels_to_others_post), or
• Manage tags (allow_manage_labels)

When neither permission is granted — or when it is overridden to Deny at the board or category level — the server rejects the entire mutation with a DataFetchingException, which surfaces in the UI as the "Autosave Recovered" message.

The "Add tags to own posts" permission is not sufficient here, because the event belongs to a different user.

Resolution

Step 1: Grant "Add tags to any post" at the role level

1. Go to Settings > Users > Roles and Permissions.
2. Click Edit next to the affected role (e.g., EventManager).
3. Scroll down to the Tags section.
4. Set "Add tags to any post" to Grant.
5. Click Save.

Step 2: Verify board-level overrides

1. Go to Settings > Community Structure and navigate to the Event board(s) where the issue occurs.
2. Open Board Permissions.
3. Confirm that the Tags permissions for the affected role are not overridden to Deny at the board level.
4. If overridden, change them back to Inherit or Grant.

Step 3: Test the fix

1. Log in as a user with the affected role (or use Switch Member).
2. Open an existing event created by a different user that contains at least one tag.
3. Click Edit, make a minor change, and click Publish.
4. Confirm the publish completes successfully without the "Autosave Recovered" message.

Quick Diagnostic Test

To confirm that tags are the root cause before changing permissions:

1. Edit the affected event.
2. Remove all tags from the event.
3. Click Publish.

If the publish succeeds without tags, the tag permission is confirmed as the cause.

Additional Information

• This issue is specific to events (and other content types) that contain tags and were created by a different user than the one editing. Editing your own tagged events only requires "Add tags to own posts."
• The permission hierarchy in Aurora flows from community level down to category, group hub, and board level. A Deny at a lower level overrides a Grant at a higher level. Always check both the role-level and board-level settings.
• The "Autosave Recovered" message is misleading in this scenario — it implies a client-side browser storage issue, but the actual failure is a server-side permission rejection.
• To verify permissions for a specific user, use Settings > Users > Roles and Permissions > Member Permissions Lookup and search for the user.

FAQ

Q1: Why does the error show "Autosave Recovered" instead of a permission error?
A1: The Aurora editor's autosave mechanism detects that the publish (GraphQL mutation) failed and falls back to its autosave recovery state. The UI does not surface the underlying server-side permission error directly, so the "Autosave Recovered" toast is displayed instead.

Q2: The role already has "Edit all events" granted. Why is a separate tag permission needed?
A2: In Aurora, event editing and tag management are governed by independent permission sets. The "Edit all events" permission allows modifying event content, but the publish payload also includes the tag array. The backend validates tag permissions separately, so both must be granted for the publish to succeed.

Q3: Will this affect other content types like blog posts or forum topics?
A3: Yes. The same tag permission requirement applies to any content type where a user edits another member's post that contains tags. If the role only has "Add tags to own posts," editing another user's tagged content will fail similarly.