About Strategy Users

Strategy is retiring legacy administration tools in phases as capabilities move to Workstation, now available in the browser. December 2026 is last supported release for server legacy tools including, Developer, Command Manager, and Object Manager. For more information on legacy tool end of support, see Legacy Tools & Platform: End of Support Reference. For feature level details, see the Workstation vs Legacy Tools Feature Parity dashboard.

Like most security architectures, the Strategy security model is built around the concept of a user. To do anything useful with Strategy, a user must be authenticated and authorized. The user can then perform tasks such as creating objects or executing reports and documents, and can generally take advantage of all the other features of the MicroStrategy system.

Strategy supports a single sign-on for users in an enterprise environment that consists of multiple applications, data sources, and systems. Users can log in to the system once and access all the resources of the enterprise seamlessly. For more details about implementing single sign-on in Strategy, see Enable Single Sign-On Authentication.

Users are defined in the Strategy metadata and exist across projects. You do not have to define users for every project you create in a single metadata repository.

Each user has a unique profile folder in each project. This profile folder appears to the user as the "My Personal Objects" folder. By default other users' profile folders are hidden. They can be viewed by, in the Developer Preferences dialog box, in the Developer: Browsing category, selecting the Display Hidden Objects check box.

Administrator is a built-in default user created with a new Strategy metadata repository. The Administrator user has all privileges and permissions for all projects and all objects.

One of the first things you should do in your Strategy installation is to change the password for the Administrator user.