> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/designer/configuration/initial-configuration.md).

# Initial Configuration Steps

Summarizes the first essential steps of Designer configuration.

This guide is intended to provide you with general recommendations for the minimum initial configuration steps of the Designer Application within your organization.

Best-practice is to perform configuration work on a non-production instance e.g. development instance and migrate the configuration through XML file exports to the production instance in a controlled way.

{% hint style="info" %}
**ServiceNow Admin rights required**

To perform the initial configuration you need ServiceNow System Admin rights. Please contact your ServiceNow Admin for further support!
{% endhint %}

## Initial Configuration Steps

The fastest way to start using Designer is to:

1. Install Designer, and
2. Assign access rights to the users.

Designer is already pre-configured, but we don't know which tables you are using in ServiceNow. So our recommendation is the following:

3. Configure Class Definitions and cross-scope privileges (CSDM tables & relationships) you want to use and ensure the Class Definitions and Cross-Scope privileges are in alignment with your target metamodel.
4. Setup preferred shapes for your organization.
5. Setup your License Management Dashboard to track the available vs. consumed licenses.

## Enhanced Configuration Options

This will provide you a quick start within the first hour, but Designer can do much more. For that, you should have a closer look at the following articles:

* Global Settings
* Global Templates
* Global Filters
* Class Fields
* Realtime indicators
* Relationship Definitions
* Relationship Fields
* Customize Commit Button
* Approval Workflow
* Editing Shape Stencils


---

# 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.ins-pi.com/designer/configuration/initial-configuration.md?ask=<question>&goal=<user_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.