# Dictionary ## Identifier The identifier lets you identify a user with a unique user ID that you choose. An optimal identifier will be something that doesn't change, like a database ID. It's a good idea to put a bit of thought into what you use as an identifier. A few key inputs on how to select a good identifier: * The user should not be able to change the identifier, i.e. don't use an email address, name, etc. as identifier. * The identifier should be accessible all places where you want to use Legal Monster, so don't use something that only lives in your mobile apps and not in your web-app, etc. ## Projects In Legal Monster everything is tied to a project. A project holds multiple agreements, widgets, user consents in the audit trail, etc. An account can have multiple projects. Projects can be used for multiple purposes, some listed here: * To separate your test environment from your production environment when developing using our [API](/docs/documentation/legal-monster-api.md) or our [widgets](https://docs.legalmonster.com/legaljs). * To separate different products, for example, a gaming studio that has different published games might give each game its own project. * To separate languages, e.g. one project for English, one for Danish, etc. ## Widgets Every project can have a variety of differently-configured widgets, which are used to obtain consent in different circumstances. This variety includes, among others: * Separating different segments of users, like business users (B2B) from consumer users (B2C). * Requesting different types of consent, such as consent to your Terms of Service, or consent to receive email marketing. * Collecting cookie consent. --- # Agent Instructions: 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: ``` GET https://docs.openli.com/docs/getting-started-1/dictionary.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.