> For the complete documentation index, see [llms.txt](https://support.meetuma.ai/uma-knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.meetuma.ai/uma-knowledgebase/getting-started/services/tips-and-best-practices.md). # Tips & Best Practices ### Setup tips * Use clear naming conventions for service items to help users find what they need quickly * Limit categories per building to avoid confusion and clutter * Review and clean up unused services periodically to keep the list relevant * Use descriptions wisely to clarify details like setup time or lead time required ### Approval tips * Set up category-level approvers early to ensure requests are routed correctly from day one * Use cost centre-level approvers only where different budgets genuinely require different sign-off * If a category doesn't need approval, leave the approver blank — requests will auto-approve ### Cost centre tips * Set up cost centres before rolling out services to users so costs are tracked from the start * Use team restrictions to keep the dropdown clean and relevant for each user * Deactivate rather than delete cost centres to preserve historical reporting data --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://support.meetuma.ai/uma-knowledgebase/getting-started/services/tips-and-best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.