Revyz Command Center for Confluence
Revyz Command Center for Confluence
Breadcrumbs

User Impersonation

About this Page

The User Impersonation feature in Revyz Command Center for Confluence ensures that when data is restored, the original authorship and ownership metadata remains intact. Instead of the restored content appearing as if it were created by the "Revyz App" or the administrator who triggered the restore, Revyz "impersonates" the original user to maintain an accurate audit trail and historical record within Confluence.

What is the Use Case?

In a standard API-based restore, restored pages often show the person who initiated the restore (the Admin) as the author. This creates several issues that User Impersonation solves:

  • Audit & Compliance: Organizations need to know who originally created a document or comment for legal or internal compliance reasons.

  • Data Integrity: Maintaining the original "Created By" and "Author" information ensures the historical context of the documentation is preserved.

  • Collaboration: When footer comments are restored, seeing the original commenter’s name (rather than a generic app name) allows team members to know exactly who provided the feedback.

  • Fallback Protection: In scenarios where the original user no longer exists in the Atlassian directory, the system provides a graceful fallback to the Revyz App as the owner, preventing restore failures.

This feature is applicable to:

  • Spaces

  • Pages

  • Blogs

  • Footer Comments (associated with Pages and Blogs)

How this Feature Works

When you trigger a restore job through the Revyz Command Center, the User Impersonation logic runs automatically in the background.


Selection & Triggering

Navigate to the restore section (e.g., Data Security & Compliance > Pages Restore) and select the snapshot and items you wish to restore. During this process, you can select your destination space.

Let’s take an example: Select the desired page/blog you wish to restore and check its creator name.

image-20260415-184644.png
User Mapping

As the restore job progresses, Revyz identifies the original author of the Page, Blog, or Comment from the backup snapshot.

  • If the user exists: Revyz matches the user ID and attributes the restored content to that specific user.

  • If the user does not exist: If the original author has been deleted from your Atlassian site, the owner defaults to the Revyz App.

For more, refer the FAQs section below.


Step 1: Navigate to Data Security and Compliance > Restore > Pages. Select the desired source site, snapshot, and space.

image-20260416-044144.png

Step 2: Select the desired destination site, snapshot, and space.

image-20260416-060249.png


Step 3: Select the desired page you want to restore. Check its creator name.

image-20260416-061032.png

Step 4: Configure your parent and child page restoration settings and click View summary to review the details before proceeding.

image-20260416-044933.png

Step 5: Review the summary of your selected pages and restoration settings, then click Restore to initiate the process.

image-20260416-045202.png

Step 6: Add job notes, if required.

image-20260416-045846.png

Step 7: You’ll see the job running under “Restore and Deploy Jobs”. You can monitor the progress of these restores via the Restore Job Details page in the Revyz Command Center, where you can add job notes (e.g., "Testing User Impersonation") to track your administrative actions.


image-20260416-050219.png

Step 8: The job will run from “Running” to “Success”.

image-20260416-050320.png

Step 9: Review the summary of your selected pages and restoration settings, then click Restore to initiate the process.

image-20260416-053803.png

Step 10: Once the job moves from "In Queue" to "Successful," you can verify the impersonation in your Confluence destination space:

  • Page Ownership: Check the page metadata; the "Created by" section will reflect the original author rather than the admin who performed the restore.

  • Comments: Scroll to the footer comments; the avatars and names will mirror the original commentors, preserving the timeline of the conversation.

image-20260416-063014.png


Frequently Asked Questions (FAQs)

What happens if the original content creator is not present on the destination site?

If the user associated with the original content (such as a space, page, blog, attachment, or footer comment) is not present on the destination site, Revyz will restore that item with Revyz as the owner/creator.

What content can Revyz restore?

Revyz supports the restoration of Pages, Blogposts, Footer comments, Attachments, Spaces, and Templates.

What is the goal of the new restore process?

Our goal is to create an exact replica of the item from your source site onto your destination site. Previously, some items were restored with Revyz as the creator rather than the original user; we have improved this to maintain original ownership whenever possible.

What is the goal of the new restore process?

Our goal is to create an exact replica of the item from your source site onto your destination site. Previously, some items were restored with Revyz as the creator rather than the original user; we have improved this to maintain original ownership whenever possible.

What happens if a user from the source site is not on the destination site?

If a user cannot be found on the destination site, Revyz acts as the default fallback. To keep the process moving, any items owned by that missing user will be restored with Revyz as the owner.

How will I know if Revyz took ownership of an item?

A restore user log will notify you whenever this happens.

Can I choose a specific user to be the "fallback" owner if the original user is missing?

Currently, this is a limitation. Revyz does not yet provide settings that allow customers to designate a specific account ID as a custom default fallback; it defaults to the Revyz account.

Does Revyz restore the settings of the content along with the content itself?

No, Revyz does not restore the specific settings of any content during the restore process.

Restoring Spaces

Who will own my restored Space?

  • If the user is present: The space is restored with the original owner.

    If the user is missing: Revyz will be set as the owner.

What if the space creation fails for a specific user?

If we cannot create the space under a specific user's ID, we assume that user is not present on the site. We will then restore all subsequent content for that user (pages, blogs, etc.) with Revyz as the owner.

Restoring Pages

How is page ownership handled?

Pages have both a Creator and an Owner. By default, the creator is also the owner, but these can be different people.

  • Both users present: The page is restored with the original creator and owner.

    Creator missing, Owner present: Revyz becomes the creator, but the original owner remains the owner.

  • Both users missing: Revyz is set as both the creator and the owner.


Restoring Blog posts

Who is listed as the author of restored blogs?

  • If the user is present: The blog is restored with the original owner.

    If the user is missing: Revyz is set as the owner.

If blog creation fails for a user, all other items (attachments, comments) for that user will automatically default to Revyz ownership.


How are attachments and comments attributed?

  • If the user is present: They are restored with the original owner.

    If the user is missing: Revyz will be listed as the owner.

    • Automatic Fallback: If an attachment or comment fails to link to a user, the system assumes that user is missing and uses Revyz for all remaining items by that person.