Segments and dashboards
Keep useful views of your operational data close at hand.
Use segments for repeatable views
A segment is a named filter, such as active customers or tickets waiting for a reply. Apply it to a collection instead of rebuilding the same filters each time. A segment narrows the records you can already access; it never grants additional permissions.
Developers can also define segments in a plugin when a filter is part of application logic.
Build an overview
Use the project's dashboard and chart tools to summarize connected data. Give charts clear names and units so teammates know what they are looking at. Verify the underlying collection, environment, and filters when interpreting a result.
When AI query generation is available on your plan, describe the question in ordinary language. Review the resulting fields and filters before relying on the answer. Query generation uses the schema to propose a query; record access remains enforced by the agent.
When a view is slow
Large exact counts, broad text searches, and sorts without matching indexes can be expensive. Start with a narrower filter. Ask a developer to inspect database query plans for frequently used views rather than adding a dashboard refresh loop.