> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/administration/install-configure/rebuilding-the-s-docs-app-in-an-org.md).

# Rebuilding the S-Docs App in an Org

{% stepper %}
{% step %}

### Navigate to the App Manager

Go to the App Manager from Setup.
{% endstep %}

{% step %}

### Create a new Lightning App

Click the ‘New Lightning App’ button.
{% endstep %}

{% step %}

### Name the app

Fill in the App Name field with “S-Docs”. The Developer Name field should automatically fill in as “SDocs”. Click Next.
{% endstep %}

{% step %}

### App Options

The default App Options can be left as they are. Click Next.
{% endstep %}

{% step %}

### Utility Items

No Utility Items need to be added. Click Next.
{% endstep %}

{% step %}

### Navigation Items

On the Navigation Items page, move Home, S-Docs Templates, S-Docs Jobs, and S-Docs Setup from the Available Items panel to the Selected Items panel. Click Next.
{% endstep %}

{% step %}

### User Profiles

On the User Profiles page, move System Admin and any other profiles from the Available Profiles panel to the Selected Items panel. Click Save & Finish.
{% endstep %}

{% step %}

### (Optional) Show in App Launcher short list

To have it show in the App Launcher short list go to Setup > App Menu and drag it up the list.
{% endstep %}
{% endstepper %}


---

# 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://help.sdocs.com/sdocs/administration/install-configure/rebuilding-the-s-docs-app-in-an-org.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.