Projects and organizations
How TraceX organizes your company, your products and their systems. Organizations, projects, restricted projects and the company profile.
TraceX has two levels: your organization (the company) and its projects (the products or systems inside it). Getting this structure right matters, because an investigation only looks at the sources connected to its project. That keeps answers focused and access tight.
Organization
Section titled “Organization”Your company’s TraceX workspace. It holds:
- your team and their roles,
- your plan, seats and billing,
- security settings: single sign-on, two-factor sign-in, data controls and logs,
- every project.
Everyone you invite joins the organization. Most companies have exactly one.
Projects
Section titled “Projects”A project is one product or production system. Each project has its own:
- connected repositories, databases, log stores and error trackers,
- investigations and conversations,
- knowledge base (runbooks, docs, notes),
- integrations that send it issues (Slack channels, a support inbox, Jira, …).
Switch projects with the switcher at the top of the sidebar. Plans limit how many projects and connected sources an organization can have (Plans).
How to split your systems into projects
Section titled “How to split your systems into projects”| Your setup | Suggested projects |
|---|---|
| One product, one backend | One project. |
| One product with a web app, a mobile API and a data warehouse that all share data | One project, so an investigation can follow an issue across all of them. |
| Two unrelated products with separate teams and databases | Two projects, so each team’s issues only look at their own systems. |
| A sensitive system only a few people may see | Its own restricted project. |
A good rule: if an engineer investigating an issue would need to look at both systems, put them in the same project.
Restricting a project
Section titled “Restricting a project”Admins can restrict a project to chosen members. Others don’t see it, its investigations or its conversations.
Company profile
Section titled “Company profile”TraceX reads your databases and repositories live and keeps no copy of them. What it does keep is what your team writes about its systems, in the company profile:
- the project overview: what the product does and how it’s built,
- notes on each connected source: what a table, collection or module is for, and
anything surprising about it (“
orders.totalis in dollars, not cents”), - facts TraceX learned when someone corrected a root cause.
These notes make a real difference: they are the context a new engineer would get in their first week. Anyone can read the profile; admins edit it.