Client records
Keep business details together for the team working on the relationship.
AMS · Connected business workflows
Organize client and brand records so the team knows who the work belongs to.
Teams managing client relationships and the brands attached to that portfolio.
The team needs to distinguish the client relationship from the brand identity used in projects, publishing and conversations.
Fictional example: Forma Studio is the client and Forma / Autumn collection is the associated brand context. This website example makes no live changes.
People can identify who the work serves and which brand’s accounts and activity belong with it.
Give the business context a home that your projects, publishing and conversations can refer to.
Keep business details together for the team working on the relationship.
Give each brand its own working context.
Organize social integrations under the relevant brand.
Extend supported records with the fields your team needs.
Know which client or brand the work serves.
Use the applicable permissions and data scopes as the portfolio grows.
No. Your team can organize internal projects without a client or brand. This particular example demonstrates the optional client context; brand records themselves belong to a client record.
No. Account connections and the relevant access must be configured separately. Brand and user limits also depend on the workspace plan.
Brand and user limits depend on plan. The sample businesses and people shown are fictional.
Read how each connection helps before choosing whether to open another page. Moving between tools does not itself configure an automatic handoff.
Add client or brand context to the projects that need it.
Give every task an owner, a deadline and the context to move forward.
Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.
Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.
Optional: explore the full Projects & tasks story ↗Select the appropriate connected brand account when composing a post.
Compose, organize and schedule social content by brand and connected account.
Fictional example: Forma Studio’s Instagram collection post is scheduled for 21 October at 11:00.
Publishing requires a paid plan. Supported media, post types and scheduling behavior vary by provider, account and permissions.
Optional: explore the full Social publishing story ↗Handle supported conversations within the relevant brand identity.
Bring supported brand conversations into a shared place for the people handling them.
Fictional example: Lina asks Forma Studio whether the collection is available in store; Nour reviews a suggested reply.
Inbox requires a paid plan. Supported message types, reply windows and channel capabilities vary by provider.
Optional: explore the full Social inbox story ↗