Patterns
Use Case: Clients & Client Teams
Track client accounts, the internal teams assigned to them, and everything that happens around those relationships.
If your organization manages external accounts — whether that's customers, portfolio companies, agency clients, or strategic partners — custom objects give you a proper place to keep that data inside Atomicwork rather than in a shared spreadsheet that drifts out of date the moment someone changes teams.
This pattern is common in professional services, managed IT, consulting, and customer success.
What You're Modeling
A Client is a standalone record representing an external organization. It exists independently — it's not tied to a single internal employee and it's not a ticket. It has its own identity, status, and attributes.
Client Team isn't a separate object — it's represented by relationship fields on the Client record. You link multiple internal employees to the client directly: one as the account owner, others as team members. Because these are relationship fields pointing to your actual user directory, the data stays current automatically as people change roles or leave the organization.