> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/planning-and-installation/existing-customers.md). # Moving from the previous console If your organization used the previous AMIE console, your deployment has been migrated into AMIE Advanced for you. No additional work is required. Sign in at **my.spectralink.net** with the email address and password you already use, and you land in the new console, in your existing deployment — which AMIE calls your [Space](/amie-advanced/introduction/how-your-space-is-organized.md). ## How your deployment maps The previous console organized a deployment as an **Account** containing **Organizations**, each containing **Locations**. AMIE Advanced organizes a deployment as a Space containing a tree of groups; a group beneath another group is a subgroup. The two shapes line up one for one, with one addition: each Location also becomes a site. ```mermaid flowchart LR subgraph Before["Previous console"] direction TB ACC["Account X"] OA["Organization A"] OB["Organization B"] LC["Location C"] LD["Location D"] ACC --> OA ACC --> OB OA --> LC OB --> LD end subgraph After["AMIE Advanced"] direction TB SP["Space X"] GA["Group A"] GB["Group B"] SC["Subgroup C"] SD["Subgroup D"] SP --> GA SP --> GB GA --> SC GB --> SD end ACC -.-> SP OA -.-> GA OB -.-> GB LC -.-> SC LD -.-> SD ``` Each Location (C and D above) also becomes a site carrying its address. | In the previous console | In AMIE Advanced | | --------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Your Account | Your Space — the group at the top of the tree | | An Organization | A group directly beneath the top | | A Location | A subgroup beneath its Organization's group, and a site carrying its address | | A device in a Location | Placed in that Location's subgroup | | A device with no Location, or whose Location was not migrated | Placed in the group at the top of the tree | | A user assigned to one Location | Placed in that Location's subgroup | | A user assigned to several Locations in one Organization | Placed in the Organization's group | | A user assigned across several Organizations, or to no Location | Placed in the group at the top of the tree | | A user with an administrator or super user role | **Admin** | | A user with a read-only role | **Viewer** | | A user with any other role | **User** | Nobody is migrated as **Owner**. What each role can do is on [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md). Your licenses, devices and batteries are read through the new structure without being copied. The group selector in the console header shows the tree; see [The group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector). ## What is different The hierarchy has the same shape, but it is not fixed at three levels and not tied to physical places. You can add groups and subgroups beneath any group, name them for teams and departments rather than buildings, and place new users in any of them — see [Planning your groups](/amie-advanced/planning-and-installation/planning-your-groups.md) for what that makes possible. Your handsets keep reporting as before. Their AMIE Agent settings do not need to change. ## Signing in for the first time Sign in at **my.spectralink.net** with your existing email address and password. If you have forgotten your password, choose **Email Code** on the sign-in screen and a one-time code is sent to your email address — see [How AMIE works](/amie-advanced/introduction/how-it-works.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.spectralink.net/amie-advanced/planning-and-installation/existing-customers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.