> ## Documentation Index > Fetch the complete documentation index at: https://docs.floral.so/llms.txt > Use this file to discover all available pages before exploring further. # Your account and team accounts > Understand the 2 kinds of connected accounts, who can use them, what administrators control, and what happens when someone leaves. Assistants can work in other apps your team uses, such as Gmail, Linear, or Stripe. Each connection to such an app is one of 2 kinds: **Your account** or a **Team account**. The difference decides who can use it, who it acts as, and where it works. ## At a glance | | Your account | Team account | | - | - | - | | Who connects it | You | An administrator | | Who it acts as in the other app | You | The company account, or the person whose login was used | | Who can use it | Only you, with every assistant that supports the app | Everyone who uses an assistant the administrator allowed it for | | Where it works | The Floral app, Slack direct messages, private Slack replies, and your own routines | Everywhere, including Team replies in Slack and routines for everyone | | Who can remove it | You | An administrator | | When the person leaves | Removed from Floral | Company keys keep working. A login that belonged to the person stops working | ## Which apps are which | App | Kind | Why | | - | - | - | | Gmail, Google Calendar, Google Sheets | Your account only | You sign in as yourself. Your mail, calendar, and files are yours. | | Notion, Linear, custom connection | Your account or a team account | Each person can connect their own login. An administrator can also connect one for the team. | | Stripe, PayPal, Traede, Shopify, e-conomic, Billy, Smoobu | Team account only | They connect the company's own account with a company key or a business login, so they belong to the team. | The rule of thumb: when a person signs in, it is **Your account**. When a company key, token, or business account is used, it is a **Team account**. ## Connect your own account Go to **Settings > Assistants > Connections** and choose the app under **Explore connections**. Sign in to the app and approve the access it asks for. For Google apps, you choose which Google account to connect. The account now appears under **Your accounts** and works for you with every assistant that supports that app. On each assistant's settings page it is marked **Available to you automatically**. There is no separate step per assistant. You don't have to connect everything up front. When you ask for something that needs an app you haven't connected, Flora tells you which app she needs and gives you a link to connect it. Connect it and ask again. Your account only works when **Connected apps** is on for the assistant and the app is allowed in the workspace. If an app is missing from the list, ask an administrator. ## What an administrator controls * **Connected apps** for each assistant. When it is off, that assistant uses only Floral data. * Which apps the workspace can use at all, under **Available services** on the Connections page. A turned-off app stops working for every assistant, and connected accounts are kept. * Team accounts. Only administrators can connect them, so members see them under **Team accounts** marked **Managed by administrators**. On each assistant's settings page, an administrator selects **Use with this assistant** or **Remove from this assistant** for each team account. Members see **Ask an administrator** instead. Administrators can't use your account, and they can't read your mail or calendar through Floral. ## When everyone acts as one person Some team accounts are connected by signing in as a person, such as Linear or Notion. Everyone who uses that team account then acts as that person in the other app. In Linear, for example, every issue shows as created by them. When an administrator connects or reconnects such an account, Floral asks them to confirm it. The account then shows **Everyone acts as** and that person's name or email under **Team accounts**. Every approval card that uses it says **Acts as** and the same name or email. Prefer a service account: a separate login for the team, such as [ops@yourcompany.com](mailto:ops@yourcompany.com). Actions then don't look like one colleague's, and the connection keeps working when a colleague leaves. Team accounts with a company key, such as Stripe, Shopify, Billy, or e-conomic, don't act as a person, so their cards don't show this line. ## When someone leaves the workspace When an administrator removes a member: * The member's own accounts are removed from Floral, together with their stored sign-in. * Their private conversations, routines, and skills are deleted. * Team accounts connected with their login stop working, and Floral deletes the stored sign-in. An administrator must reconnect the account, ideally with a service account. * Team accounts that use a company key keep working. * Routines for everyone that they owned are paused. They stay in the list for an administrator to handle. Removing someone from Floral doesn't remove their access to the other app. Remove them there as well, for example in Google Workspace or Linear. ## Remove access * **Your account**: open **Settings > Assistants > Connections**, choose the connection, and select **Remove**. It is disconnected from every assistant. You can also withdraw Floral's access in the app itself, for example in your Google account's security settings. * **Team account**: an administrator removes it the same way. They can also select **Remove from this assistant** on one assistant's settings page, turn off **Connected apps** for an assistant, or turn off the app under **Available services**. Removing a connection stops future use. It doesn't undo changes an assistant already made. ## What other people can and can't see * Colleagues can't see or use your accounts. * Colleagues can't see your private conversations or what an assistant read from your accounts. * In Team replies and in routines for everyone, assistants never use anyone's own account. * Anyone who uses an assistant can ask it to read from the team accounts it may use. Connect only what the whole team may see. * If you share a private Slack reply in a thread, everyone in the thread can read it. Check it for personal details first. ## Example: 2 colleagues, 3 apps Sofie is an administrator and Jonas is a member of the Sales workspace. She turns on **Connected apps** for Flora. She connects the company's Stripe as a team account and allows Flora to use it. Sofie and Jonas each connect their own Gmail. Neither can see the other's mail. Jonas connects his own Linear. Sofie hasn't connected Linear. What happens next: | Request | What Flora does | | - | - | | Jonas, in the app: "Which Stripe payments failed this week? Draft an email to each customer." | Reads the team's Stripe and prepares drafts in Jonas's Gmail. The approval card says **Your account**. Sofie can't see the drafts. | | Jonas: "Create a Linear issue to follow up." | Proposes an issue in Jonas's own Linear. It is created as Jonas after he approves. | | Sofie: "Create a Linear issue to follow up." | Tells Sofie she needs to connect Linear and gives her the link. | | Jonas mentions Flora in #finance, where Flora uses **Team replies** | Can read the team's Stripe for everyone in the thread. Can't use Jonas's Gmail or Linear, and suggests he asks in a direct message. | | Jonas leaves the workspace | His Gmail and Linear are removed from Floral. Stripe keeps working, because it is the company's account. | If Sofie had connected Linear as a team account with her own login instead, every issue from the team would show as created by Sofie, and the connection would stop working if she left. A service account avoids both.