> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/accounts/concepts/glossary.md). # Glossary If you come across a word and are not sure exactly what it means, look it up here. | Term | Definition | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Administrator | Permission that grants control of an organization. It is an example of a role: the same user can have a different permission in each organization. | | Scope | How much of what you see fits on a screen: your global view (all your organizations) or a single organization. | | Client | Company you provide service to. Within Plenit, it is just another organization, which you access with your own account. | | Main contact | The main contact person for an organization. | | Account | Your personal identity in Plenit: a single user, with your email, your password, and your details. It is the same across all your organizations. | | Security email | Email address associated with your account to recover access and receive security alerts. | | Session status | Status of a login session: Active (open and in use), Inactive (not in use at the moment), or Closed (ended). | | User status | Whether a user is enabled or disabled to access the platform. | | Event | Each action or access that is recorded in your account or in your subscriptions. | | Home | The dashboard level with your global view: it brings together, aggregated across all your organizations, your organizations, subscriptions, users, and events. | | My Profile | The personal side of your account: your details, your security, the organizations you belong to, and your activity. | | Organization | Company or work environment within Plenit, with its subscriptions, users, customization, and data. | | Main organization | The reference organization for your contact details. | | Permission (role) | What you can do within an organization (for example, Administrator). It is per organization, not global. | | Overview | The Home cover: the overview of your activity, with counters for organizations, subscriptions, and users. | | Industry | The industry of an organization. | | Service | The type of product a subscription corresponds to (Servers, Remote Desktop, Disaster Recovery, storage, among others). | | Subscription | A contracted service within an organization. | | User | A person with an account in Plenit. The same user can belong to several organizations, with a different role in each one. It is equivalent to your account. | | Two-step verification | Extra layer of security when signing in, using an authentication app (for example, Google Authenticator). | | Global view / organization view | The two ways to see your resources: the total from Home, or only those of one organization from the Organization level. | | Zone | The location (region or data center) where a subscription is deployed; for example, EU-MAD3 or EU-PAR1. | ### Next steps * Go back to the key ideas in [Concepts.](/docs-en/platform/accounts/concepts.md) * Put into practice what you've learned in the [How-to guides.](/docs-en/platform/accounts/how-to.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.plenit.com/docs-en/platform/accounts/concepts/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.