> ## Documentation Index > Fetch the complete documentation index at: https://docs.daoco.org/llms.txt > Use this file to discover all available pages before exploring further. # Browser profiles > Keep a signed-in browser session for a social account or any site, and choose what Daoco may do there. A browser profile is a saved, signed-in browser session that belongs to one brand. Daoco uses it to work on a website as that brand: read a dashboard, check a profile, edit a document, or post with your approval. You sign in yourself. Daoco keeps the session, never your password. Profiles live on the **Browser** tab of **Connections**. For what happens while Daoco works in one, including watching it live and taking control, see [Browser automation](/connections/browser-automation.md). ## Two kinds of profile | Kind | Where it comes from | Shown as | | - | - | - | | **Social account** | A connected account under **Socials** on LinkedIn, Instagram, Facebook, X, Threads, TikTok, YouTube, or Bluesky. Each account can have one browser sign-in alongside its normal connection. | The platform name and the account handle, under **Social accounts**. | | **Site** | Any other website you add yourself, such as an analytics dashboard, a design tool, or your CMS. | The site's address and who signed in, under **Sites**. | When a brand has both kinds, the tab groups them under **Social accounts** and **Sites**. Reddit has no browser sign-in. Reddit posts are handed off through pre-filled links you open yourself. ## Add a site **1. Open the Browser tab** Go to **Connections**, choose **Browser**, then **Add a site**. **2. Enter the address** Enter the address you sign in at, such as `https://app.example.com`. If you leave off `https://`, Daoco adds it. **3. Sign in yourself** A secure browser window opens on the site. Complete the login there, including single sign-on, MFA, or a CAPTCHA. **4. Confirm** Back in Daoco, choose **I'm signed in**. Daoco saves the session and the row shows **Signed in**. A site profile needs an address that: * uses https, * is a public site (not `localhost`, an IP address, or a private or internal name), * does not contain a username or password, and * is not a supported social platform. Connect those under **Socials**, then sign in from their row on the **Browser** tab. A brand keeps one profile per site and up to 25 site profiles. Social accounts do not count toward the 25. ### Sign in to a social account Connect the account under **Socials** first. Its row then appears on the **Browser** tab with **Sign in**. Daoco checks the platform's login itself, so a social profile shows **Signed in** only once the platform confirms it. If a browser task needs a sign-in you have not done, Daoco shows a sign-in card in chat instead. ## What the status means | Status | Meaning | Button | | - | - | - | | **Signed in** | The session is saved and ready. | **Sign in again** | | **Sign-in incomplete** | A sign-in was started and not finished. | **Finish sign-in** | | **Not signed in** | A connected social account with no browser sign-in yet. | **Sign in** | For a site, **Signed in** means a person confirmed it. Daoco cannot tell whether you are logged in to a site it does not know, so it takes your word. If no cookies were saved for the site when you confirmed, Daoco warns you. Some sites keep their session elsewhere; if the site signs you out later, sign in again. Under each row Daoco shows who signed in or started the sign-in, and when the profile was last used or updated. A social profile whose account was disconnected shows **Account disconnected**. You can still remove it. **Sign in again** starts from a clean browser and replaces the saved session. ## Choose what Daoco may do Each profile has an **Access** setting. Workspace owners and admins change it. Everyone else sees it. | Access | What Daoco may do | | - | - | | **Off** | Nothing. Daoco cannot open this profile. | | **Read only** | Look around and read. Any change is refused outright, not sent to you for approval. | | **Ask** | Changes follow the brand's [approval preference](/account-and-billing/approval-preferences.md). This is the default. | | **Allow** | Ordinary edits, form fields, and saving run without asking. Publishing and sending still follow the brand's approval preference. Deleting always asks. | How each kind of change is decided: | Change | Examples | Ask | Allow | | - | - | - | - | | Edits in the site | Edit a document or design, fill a form, save | Asks once per task per site under **Ask before acting**. Runs without asking under **Work autonomously** or **Full autonomy**. | Runs without asking. | | Publish and send | Publish, share, submit, send, schedule | Asks each time, naming the page and the button, unless the brand is on **Full autonomy** or you allowed publishing on this site. | Same as **Ask**. | | Delete and remove | Delete, remove, archive, unpublish | Asks every time. | Asks every time. | A button Daoco cannot place in one of these counts as publish and send. On a site that is not a social platform, a like, a vote, or a follow also counts as publish and send. Changes you allowed ahead of time are listed under the profile, for example "Changes allowed without asking in one conversation", with **Revoke**. Owners and admins see and revoke them. See [Approvals](/connections/browser-automation.md#approvals) for where they come from. ### Always asks These need a person to approve that exact action every time. No access setting, approval preference, earlier approval, or **Bypass approvals** skips them: * **Deleting** anything. * **Security settings** on any site: passwords, two-factor, sessions, API keys, team members and roles, permissions. * **On social accounts**: likes, reactions, and reposts; follows, connection requests, and subscribes; direct messages; posts, comments, and replies. A post or reply card shows the exact text. One approval covers one action, so Daoco cannot run bulk engagement. Platforms can restrict accounts for automated activity. **LinkedIn's terms prohibit automated activity, and approving does not remove that risk.** The approval card says so. ### Never done Daoco refuses these in a browser. There is no approval for them; it stops and tells you: * buying, checking out, or starting, upgrading, or renewing a paid plan, * entering or changing payment or billing details, * launching an ad campaign or changing an ad budget or bid, * typing a password, a one-time code, or a recovery code. Ad spend through a connected ad platform integration is separate and follows that integration's rules. Daoco reads what each button and field is from the page itself and checks every click, key press, and field before it touches it. Text on the page can only make a control count as riskier, never safer, and is never followed as an instruction. ## Remove a profile Open the row's **⋯** menu and choose **Remove profile**. Daoco deletes the saved session first, then the profile, its **Access** setting, and any changes allowed ahead of time on it. If the saved session cannot be deleted, the profile is kept and you can try again. For a social account, removing the browser profile does not disconnect the account. Its normal connection keeps working, and the next browser task asks you to sign in again. Anyone with access to the brand can add a site, sign in, and remove a profile. Transferring the brand to another workspace removes all of its browser profiles, because each one is signed in as a person. The new owner signs in again. ## Privacy and security * **You type your own password.** You sign in in a secure browser window. Daoco never sees, stores, or types your password or one-time codes. * **Where the session lives.** The session, including its cookies, is kept in an isolated browser profile at our browser provider, Browserbase, for this brand only. Daoco stores a reference to it, who signed in, and its status. Removing the profile deletes it. * **Who can use it.** A profile belongs to one brand. Only that brand's work uses it, and only on that site's own address: Daoco cannot follow a link from a site profile to another site. Research that reads the public web never uses a site profile and browses signed out. * **Who can see the live browser.** Anyone with access to the brand can open the thread, watch the browser while Daoco works, and take control. See [Watch the browser live](/connections/browser-automation.md#watch-the-browser-live). * **What is kept as evidence.** Screenshots and the steps Daoco took are kept with the task. Passwords, cookies, tokens, and codes are left out. ## Troubleshooting | What you see | What to do | | - | - | | **"Enter a public site address."** | Use the site's public https address. Local, internal, and IP addresses are not supported. | | **"The site address must use https."** | Use the https version of the address. | | **"… signs in from its connected account."** | That site is a social platform. Connect it under **Socials**, then sign in from its row on the **Browser** tab. | | **"A brand can hold 25 site profiles."** | Remove a site you no longer use, then add the new one. | | **"No cookies were saved for …"** | The sign-in may not have finished. Choose **Sign in again**. If the site still works for Daoco, you can ignore it. | | **Sign-in incomplete** | Choose **Finish sign-in** and complete the login in the secure browser window. | | Daoco says the site signed it out | Choose **Sign in again**. A site profile stays **Signed in** until you change it, because Daoco cannot check a site's login. | | Daoco says the profile is turned off or read only | An owner or admin changes **Access** on the **Browser** tab. | | **"Could not delete the saved sign-in, so the profile was kept."** | Try **Remove profile** again in a moment. | | A social profile shows **Account disconnected** | Reconnect the account under **Socials**, or remove the browser profile. | | You can't change **Access** | Only workspace owners and admins can. | ## Related guides * [Browser automation](/connections/browser-automation.md): approvals, the live browser, and taking control. * [Approval preferences](/account-and-billing/approval-preferences.md): the brand setting **Ask** follows. * [Connect platforms](/start-here/connect-platforms.md): connecting social accounts. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.