# Tagging services ### Tagging overview Tagging services in Appear is a flexible and useful way to represent relationships across your systems, teams, and organisational structure. Tags are added directly from the **Service Details view** in the **Catalog**. You can apply them however you see fit — whether to represent environments, teams, business domains, or deployment regions. ### Tagging a service To tag a service, navigate to a service detail view and enter a new line in the editable section at the top half of the column. From there, invoke the block editor by typing '/' (forward-slash) and select **Tags**. Begin typing your tag, or select an existing one. You can add as many or as few as you like.
Use tags to organise, navigate, and assess your API ecosystem in a way that aligns with how your team or organisation works. ### Tagging concepts Tags in Appear are **not standalone objects** in the database — they only exist **in relation to services**. This means the list of available tags is simply an aggregate of all tags used across all services. When **adding a tag to a service**, we show tags from all environments and versions to encourage consistency and reuse across your system. However, when **grouping or filtering by tags**, we scope them to the current branch or environment. This ensures the results are relevant to the specific context you're viewing — like filtering only by tags used in your staging environment ### Tagging FAQs
Can my team see my tags? Yes, tags are shared across your team and organisation.
Can I delete or edit my tags? No, there is no central way to delete or manage tags once created. This facility is coming soon. If you need help with this, please [get in touch](/getting-started/get-in-touch.md).
*** If you have any queries or require support with the above instructions, please [get in touch](/getting-started/get-in-touch.md) with us. --- # 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.appear.sh/managing-your-apis/tagging-services.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.