Troubleshooting: Username Change

Learn how to resolve issues when you have changed or need to change your username in Revit.

Summary

If you use Revit Worksharing (cloud, local, or Revit Server) or non-workshared Revit Cloud Models, changing your username may cause workflow failures. These include:

• Not being able to open models.
• Not being able to Sync with Central (for workshared models) or save a non-workshared model to the cloud.
• Elements that cannot be modified by anyone because the elements are checked out to the prior (and now unavailable) username.

Please refer to the use cases below to determine the appropriate solution.

If you use Revit Worksharing (cloud, local, or Revit Server) and have not changed your username, complete these steps before changing your username:

1. Sync all local changes.
2. Relinquish all (element and workset) permissions.
3. Sign out of Revit and close the application.

If you use Revit Cloud Worksharing (i.e., not local- or Revit Server-based worksharing,) you must also complete these steps and clear your Collaboration cache:

1. Identify all folders named %localappdata%\Autodesk\Revit\Autodesk Revit ####\.
2. Delete the contents of the CollaborationCache folder beneath each of these folders.

Please note that the cache improves workflow performance, and the first attempt at opening a model after clearing the cache may be slower than normal. Normal performance will be restored as the cache is repopulated.

After all steps are completed, you can update your username, relaunch Revit, and sign in. If you have locally shared workshared models, you will need to create a new local file with your new username.

If you use Revit Worksharing (cloud, local, or Revit Server), have changed your username, and are experiencing workflow failures:

There are two options available.

Option 1: You can use the same process you used to change your username to revert to your original username. Note that your username is not the same as your email address.

This option this will restore access and functionality without any loss of unsynced, locally saved changes, however it may not be the fastest way to unblock workflow failures. Furthermore, you may not be able to restore your username. In this case, Option 2 below may be preferable.

1. Sign out of Revit and close the application.
2. Revert to your original username.
3. Follow the guidance above for “If you use Revit Worksharing (cloud, local, or Revit Server) and have not changed your username, complete these steps before changing your username.”

Note: If you don't remember your original username, you may be able to identify it from past journals by searching for the word Username. In the following example, the user's Username is my_username.

Jrn.Directive _
"Username" , "my_username"

Option 2: You can keep your original username and perform actions that will unblock workflows. The specific actions vary depending on the form of Revit Worksharing you use. Please note that these changes may result in the loss of locally saved, unsynced changes to the model.

If you use Revit Cloud Worksharing:

• If a model will not open or Sync with Central workflows are failing, they can be restored by clearing the Collaboration cache.
• If elements cannot be edited because they are checked out under an old username, access can be restored by using the Force Relinquish workflow.

If you use Revit Server or locally shared workshared models where a network license server is used:

1. Sign out of Revit but do not close the application.
2. Set the Revit username to the original username associated with your profile.
3. Follow the guidance above under “If you use Revit Worksharing (cloud, local, or Revit Server) and have not changed your username, complete these steps before changing your username.”

If you use Revit Server or locally shared workshared models where a network license server is not used:

• If a model will not open or Sync with Central workflows are failing, you can regain access by creating a new local copy using your new username.
• If elements cannot be edited because they are checked out under an old username:
  1. Have all users sync their changes.
  2. Use a new local copy to overwrite and replace the central model.
  3. Create new local copies before resuming your work.

If you use non-workshared Revit Cloud Models and have not changed your username, complete these steps before changing your username:

1. Sign out of Revit and close the application.
2. Clear the Collaboration cache:
   1. Identify all folders named %localappdata%\Autodesk\Revit\Autodesk Revit ####\.
   2. Delete the contents of the CollaborationCache folder beneath each of these folders.

Please note that the cache improves workflow performance, and the first attempt at opening a model after clearing it may be slower than normal. Normal performance will be restored as the cache is repopulated.

After these steps are complete, you can update your username, relaunch Revit, and sign in.

If you use non-workshared Revit Cloud Models, have changed your username, and are experiencing workflow failures:

There are two options available.

Option 1: You can use the same process you used to change your username to revert to your original username. Note that your username is not the same as your email address.

This option this will restore access and functionality without any loss of unsaved changes, however it may not be the fastest way to unblock workflow failures. Furthermore, you may not be able to restore your username. In this case, Option 2 below may be preferable.

1. Sign out of Revit and close the application.
2. Revert to your original username.
3. Follow the guidance above for "If you use non-workshared Revit Cloud Models and have not changed your username, complete these steps before changing your username."

Note: If you don't remember your original username, you may be able to identify it from past journals by searching for the word Username. In the following example, the user's Username is my_username.

Jrn.Directive _
"Username" , "my_username"

Option 2: You can keep your original username and clear the Collaboration Cache. Please note that this may result in loss of changes that were not saved to the cloud.

Thank you for your patience and understanding, we apologize for any confusion or inconvenience this may have caused.