Canonical page: https://tellenze.com/guides/connect-your-tools Connection setup # Your tools. A useful connection. Choose the job, prepare the right permissions and bring in the person who owns each step. Then verify one useful result before building a larger workflow. [Find your setup checklist](#connection-checklist)[Explore integrations](https://tellenze.com/platform/integrations) - Configure workspace - Authorize member - Check one result Ready connection Illustrative model · Finish the workspace setup, authorize the account and check a useful result. Choose the job first ## A connection should have a purpose. Reading repository context, sending a reviewed message and signing in each need different setup. An ongoing connection and a one-time import also serve different jobs. 01 ### Repository context GitHub or GitLab context helps a team follow commits, changes and delivery evidence. Set up repository access and link the right Projects. 02 ### Design context Figma references need workspace setup and the viewer’s own authorization. Enable the Projects where design features should appear. 03 ### Agent and API access MCP (Model Context Protocol) gives a compatible agent access to workspace tools. API Apps are named connections with selected permissions for your own systems. Choose the one that fits the job. 04 ### Reviewed email Gmail or SMTP provides a permitted sender. Preparation, review and explicit sending are separate steps. 05 ### Workspace sign-in Google or Microsoft authentication helps invited members sign in. It does not grant access to every part of the workspace. 06 ### Existing work Use a reviewed CSV import for a selected task list. Direct provider importers marked Coming soon cannot transfer data yet. [Check product availability](https://tellenze.com/availability)[Plan a CSV import](https://tellenze.com/guides/move-your-work) Find the setup owner ## The right people. A clear handoff. An administrator enables features for the workspace. The provider’s app owner supplies its setup details. Members authorize their own accounts and check the work they can access. - 01 · Administrator ### Configure and enable. Check the workspace feature, provider application, allowed repositories or Projects and shared settings. - 02 · Member ### Authorize the account. Review consent for your client, provider identity or personal sender. Use the account that should act. - 03 · Together ### Check one result. Read context you can access, check the source links and review any proposed action before authorizing it. Prepare before authorizing ## A checklist for your connection. Follow the linked Help guide and use the exact callback URL or connection address shown in your workspace. Keep credentials out of work items, documents and support messages. Repository context ### GitLab.com Setup ownerWorkspace administrator + provider account owner PrepareOne GitLab.com group or subgroup, plus a token with read_api. Use an account with the required Reporter access. AccessRepository discovery and delivery information stay within that group and its subgroups. Self-managed hosts are not supported. First checkLink one Project you can access to its repository and read the Delivery section. Event automation needs its own webhook and rule setup. [GitLab connection guide](https://tellenze.com/help/gitlab) Repository context + reviewed actions ### GitHub Setup ownerWorkspace administrator + provider account owner PrepareOne GitHub owner and a fine-grained read token for selected repositories. Review the suggested repository links or link projects manually. AccessOptional issue, branch and draft pull-request actions need a separate writing token. Webhooks and workflow automation have separate configuration. First checkRead context from one linked repository first. Review the destination and exact proposal before making a supported change in the provider. [GitHub setup guide](https://tellenze.com/help/workspace-admin#github-and-figma-connections) Design context + reviewed actions ### Figma Setup ownerWorkspace administrator, then each member PrepareA workspace OAuth app with the displayed callback and required read scopes. Enable the relevant projects; each viewer connects their own Figma account. AccessProject design features must be enabled for both the workspace and the project. Team-owned work and workspace documents follow the workspace setting. Members must consent to any additional writes. First checkOpen one design reference the viewer has permission to read using their own authorization. Ask the app owner about provider approval if wider OAuth access is needed. [Figma setup guide](https://tellenze.com/help/workspace-admin#github-and-figma-connections) Reviewed email sending ### Gmail Setup ownerWorkspace administrator, then the sending account owner PrepareA workspace Google OAuth application, enabled Gmail API and exact redirect URI. Enable Gmail before authorizing a personal or shared sender. AccessGmail authorizes sending. It does not read the inbox or import messages into Signals. First checkPrepare a draft and inspect the actual From, recipients, subject and body. Send only after explicitly authorizing the reviewed email. [Gmail and email setup](https://tellenze.com/help/workspace-admin#set-up-email-powerups) Named personal or shared senders ### SMTP Setup ownerMember for personal senders; administrator for shared senders PrepareAn enabled provider and its allowed server, port, TLS mode, credentials and From address. Give each sender a recognizable name. AccessThe provider must allow the sender address chosen for the email. Each connection can be managed separately. First checkCheck the sender shown in the draft. Saving credentials does not send an email or prove that the provider will accept delivery. [SMTP sender guide](https://tellenze.com/help/workspace-admin#set-up-email-powerups) Workspace sign-in ### Google or Microsoft sign-in Setup ownerWorkspace administrator + provider application owner PrepareRegister the provider application and use the exact callback in settings. Microsoft also needs the directory tenant ID. AccessFinish setup before enabling the sign-in method. Keep at least one usable method; disabling one can end sessions using it. First checkCheck that an invited member can use the enabled sign-in method. Signing in does not replace Project, Team or room permissions. [Workspace sign-in guide](https://tellenze.com/help/workspace-admin#choose-workspace-sign-in-methods) Workspace tools for a compatible agent ### MCP Setup ownerThe member authorizing the client PrepareAn active membership, a compatible OAuth MCP client and the endpoint shown in Settings → MCP. Review consent and choose the machine profile. AccessThe client follows the member’s current permissions and the available tool catalogue. ChatGPT has a separate private pilot path. First checkAsk the agent to discover tools and read one accessible work item. Check the context and intended operation before requesting a change. [Agent connection guide](https://tellenze.com/help/agents#connect-an-external-agent) Selected API access for your system ### API Apps Setup ownerThe App owner; administrators permit member creation PrepareCreate an App in Account settings, choose its grants and copy the token once. Keep it in the connecting system’s secret store. AccessThe App can use only its selected permissions within its owner’s current access. Workspace documents need a separate permission. Reading and changing work also need separate permissions. First checkUse the API address shown in settings to read something the App has permission to access. Follow the Apps guide for pagination, versioned writes and Required Context. [Apps and API guide](https://tellenze.com/help/apps) Verify the useful result ## Read first. Review before acting. For a repository or design connection, open one source you have permission to read. For an agent or App, start with an allowed read. Check that the account, source and destination are the ones you intended. For email, prepare a draft and check the sender shown, recipients and complete copy. After you explicitly authorize sending, check the delivery receipt. [See prepare, review and execute](https://tellenze.com/platform/powerups) Illustrative setup check · one connection at a time IdentityThe intended workspace member and provider account. SourceOne repository, design reference or work item you can already access. ActionAn allowed read, or a proposal you review before explicitly running it. ResultCheck the response, saved result or delivery receipt, and investigate any errors. A provider accepting an email does not prove it reached the recipient. If the outcome is unclear, check it before trying again. Reconnect or remove access ## When the setup changes, check it again. Credentials can expire, account permissions can change and a Project’s repository link can stop matching the intended source. Read the reported state before retrying. [Understand connection permissions](https://tellenze.com/trust) ### Expired or rotated credentials. Follow the provider guide to rotate or reconnect. Changing Gmail or Figma OAuth app credentials requires members to reconnect their accounts. ### Changed source access. Check that the same member and connection still have access. Check repository discovery again and inspect the Project’s repository link. ### Removing a connection. Revoke your MCP authorization or App when access is no longer needed. Check what disabling or disconnecting the provider changes. Earlier history can remain. ### Missing companion readiness. A local companion needs separate device pairing, provider checks and workspace permission. Follow its setup guide; a machine profile alone does not enable it. [Read companion setup](https://tellenze.com/help/agent-reactions) A few useful details ## Make the setup fit the job. Does connecting a provider enable every action it supports? Read access, writing credentials, Project links and enabled features can have separate requirements. Review the provider checklist and current settings for the action you intend to use. Can I use a self-managed GitLab instance? The current shared GitLab connection supports one GitLab.com group or subgroup. Self-managed GitLab hosts are not supported by that connection. Can Gmail bring my inbox into Tellenze? The current Gmail connection is for reviewed sending. It does not grant inbox reading or import messages into Signals. Where do I start with ChatGPT? ChatGPT has a private pilot path. [Read the pilot guidance](https://tellenze.com/help/agents#connect-tellenze-to-chatgpt) or [contact us about access](https://tellenze.com/contact). For another compatible MCP client, use the endpoint and authorization shown in your workspace. What should I include when asking for help? Include the provider, intended action, visible error and the point where setup stops. Keep passwords, tokens and client secrets out of the message. Your administrator can check workspace enablement before you contact Tellenze. Keep your next step clear ## Find the guide for your next step. [Browse all guides](https://tellenze.com/guides) COME TAKE A LOOK ## A little less busy. A lot more together. Curious? Join the waitlist and see how we welcome your team. Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace. [Join waitlist](https://tellenze.com/waitlist)Start with your email. No payment needed to join.