> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/readme/secoda-as-an-admin/customize-the-workspace.md).

# Customize the workspace

As an admin, you can change the appearance of your Secoda workspace to suit your team.

## **How to customize Secoda's appearance** <a href="#h_3a4bfd6458" id="h_3a4bfd6458"></a>

There are various personalization options for Secoda users. These personalization options are displayed to viewers when they first come into Secoda.

{% hint style="info" %}
As an Admin, you're able to "lock" some of these personalizations. If you don't lock these, then Editors and Viewers can personalize their workspace as they'd like.
{% endhint %}

### **Edit workspace logo and name**

* Go to **Settings** from the sidebar and click into Workspace Settings
* Change the Logo to your organization's logo and change the name, if applicable

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/72a730f0-cef3-481e-95a4-0dc80a49fa6d.png" alt=""><figcaption></figcaption></figure>

### Allowed Domains

If using multiple domains for your organization, you can add these domains to the "Allowed domains" section in the Security settings. This will allow members with email IDs ending in those domains to sign up to the workspace directly.

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/0714291b-b9da-4af6-8f2d-22df05a4a7a6.png" alt=""><figcaption><p>Security Settings</p></figcaption></figure>

### Edit the Homepage

You can change your personal homepage background, and Admins can edit the Team homepages as well. Simply click into **Home** and click Edit in the top right.

You can also pin resources to the homepage to point users in the right direction when they first join your workspace. To learn more about the home page, see the Custom Homepage link below!

{% content-ref url="/pages/8Lf64SudXpg75vLiSM8W" %}
[Homepage](/features/homepage.md)
{% endcontent-ref %}

{% hint style="info" %}
Not using Secoda to manage your data knowledge yet? Sign up for free [here](https://app.secoda.co) 👈
{% endhint %}


---

# 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.secoda.co/readme/secoda-as-an-admin/customize-the-workspace.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.