Your organization and team
Choose the right workspace, understand role-based access, and keep shared resources organized.
Start in the right organization #
An organization is the workspace containing your team’s Lines, workflows, contacts, connections, and databases. Select the intended organization before you create a resource or connect an external account.
If something appears missing, check the selected organization first. Resources in a different organization may not appear in the current workspace.
Use one account across organizations #
Your Chatigram account can belong to multiple organizations. Use the organization selector at the top of the application to switch to the one you want to work in.
Your Chatigram account can belong to different organizations, and each organization can include multiple Admins and Members. You can invite more teammates as your team grows. Resource allowances such as active Lines, workflows, and databases apply separately to each organization’s plan.
Each organization has its own dashboard, workflows, automations, Lines, contacts, App Connections, and databases. Organization A’s workspace data stays separate from Organization B’s workspace data. Belonging to both does not combine their resources or give one organization access to the other’s data.
For example, you can help a client in one organization and manage your own business in another using the same account. Check the selected organization before creating a workflow, connecting an account, sending a message, or reviewing usage. Switching organizations changes the workspace you are working in; it does not move or copy its data.
Manage the current organization #
Use Manage beside the currently selected organization to open its management controls. Confirm the organization name before inviting people or changing a plan.
With the appropriate Admin permissions, use those controls to review the current plan, change the organization’s plan, invite teammates, and manage membership. A subscription belongs to the selected organization; switching to another organization can show a different plan and usage.
Organization management is separate from your personal profile’s Manage account controls. See your account and devices for personal settings.
Understand your role #
An organization can have more than one person. Its two roles are Admin and Member:
An organization can have several Admins and several Members. Your role is specific to each organization: you can be an Admin in one and a Member in another without changing accounts.
| Role | Typical work |
|---|---|
| Admin | Manage the organization and its configuration, including workflows, channel setup, connections, and settings allowed by the application |
| Member | Support customers through the permitted conversation and Inbox tools without needing administrative configuration access |
Invite customer-service teammates as Members when their work is reading and answering customer conversations. Give Admin access when the person needs administrative responsibilities. A human support agent is a team member’s job; Member is the organization role to use for that support work.
If a configuration screen is unavailable, ask your organization administrator to check your role and the plan. Do not assume a shared link grants access to a protected resource.
Invite your support team #
As an Admin, select the intended organization, open Manage, and use its membership or invitation controls. Invite the intended person, choose Member for a support teammate, and have them accept the invitation. They should select the correct organization after joining.
Test with one customer conversation on a team-supported Line so the new teammate can find it in Inbox and send an appropriate reply. A Line with Private AI mode enabled does not allow human agents to view or reply to its conversations. Use the role controls to review access when responsibilities change.
See Human customer support for a practical assistant-to-team handoff, including Telegram Lines.
Keep a useful naming system #
Give Lines names that identify their channel and team. Name workflows by outcome, such as Website welcome or Daily request review. Use separate test resources when trying out a new automation.
Before deleting or changing a shared connection, table, status, or reusable definition, check the workflows that depend on it.
Share examples safely #
Review exported workflow Properties, embedded text, resource identifiers, and example data before sharing. An exported definition can describe private business processes even when it does not contain a password.
Use the protected App Connections setup for credentials, and keep support reports focused on the behavior needed to diagnose the issue.
Access and billing are separate #
A role can permit an operation while the plan limits the available resource count. Conversely, a higher plan does not automatically give every team member administrative access. See plans and limits.