# Sign in to Facebook on a cloud phone

Prepare the phone, use the live sign-in screen, optionally save credentials, choose posting identities and recover from sign-in problems.

Canonical: https://docs.lead-knight.com/en/cloud-phones/sign-in/


## What this flow does

The app shows the cloud phone's screen and relays your clicks and typing to that phone. You sign in to Facebook there, not to a Facebook session in your local browser. The Facebook session stays on the phone after the sign-in dialog ends.

## Before you start

- Be a workspace owner or admin with access to the intended profile and available cloud-phone controls.
- Have access to that Facebook account, its password and any two-factor or identity-confirmation method Facebook requests.
- Review the cloud-use disclosure. A password is optional; choose manual sign-in if you do not want to save it.
- Use the correct Facebook account. The app refuses a different account for an already-linked profile and detects accounts already assigned to another profile or cloud phone in this workspace.

## Prepare the phone

1. Open **Connections**, the Facebook-group connection's **Manage groups**, and select the profile under **Facebook profiles**. Use **Manage connection** to open its connection controls.
1. If a phone has not been set up, choose **Connect a cloud phone**. For a new Facebook profile, **+ Add profile** offers **Cloud phone** where available.
1. Wait for **Preparing the phone…**. The page explains if preparation is taking longer and you can return later when the sign-in button is available.
1. Choose **Sign into Facebook on the phone**. A connected phone also offers **Sign in again** to reopen its sign-in flow.

## Use the live phone screen

1. Wait in **Sign in on your cloud phone** while **Starting your cloud phone…** is shown. The UI estimates about 5 minutes on a first start and about 2 on later starts; these are estimates, not completion guarantees.
1. Keep the window open for Facebook to appear. If **Keep setting up meanwhile** is offered, it keeps the startup running behind the app's status bar; use **Open** to return. Ordinary cancellation is not the same as that background option.
1. Click the email/phone field on the phone screen, then type. The indicator changes from **Click the phone screen to type** to **Keyboard → phone** when the phone has keyboard focus. Click the password field and enter the password there.
1. Complete the sign-in on the phone screen. If Facebook requests a two-factor code, CAPTCHA or identity check, complete it there. Scroll the phone view when needed.
1. After **You're signed in. If Facebook asks to save your login or trust this device, confirm now.**, respond to those Facebook prompts during the displayed hold/countdown.
1. Complete **Choose your Facebook identities** when offered, selecting the person and/or Pages, then **Connect selected**. Group import follows the selected identities. If importing continues in the background, it does not require repeating sign-in.
1. Return to the connection card and check **The phone is connected**, identity readiness and any warmup message. Review [publishing-device settings](https://docs.lead-knight.com/en/extension/posting-presets/); sign-in alone does not select cloud publishing.

For keyboard navigation of the phone screen, the UI supports moving the tap point with arrow keys and pressing Enter or Space, then typing. Shift+Tab leaves the phone keyboard.

## Optional Automatic sign-in

**Automatic sign-in** offers **Facebook email or phone** and **Password**. Read the disclosure and provide the required **I agree** consent before saving; choose **I'll sign in myself** to use the live phone flow instead.

The description says normal relay typing is not saved, while credentials you explicitly choose to save for automatic sign-in are kept encrypted. **Password saved. This does not confirm a Facebook sign-in.** is an important distinction: check the actual phone connection afterwards.

The card shows saved/expiry times and when replacement is allowed. Use **Replace password** when offered. A password can only be changed once every 24 hours; follow the displayed next-change time rather than repeatedly submitting it. Automatic sign-in may still require human help for two-factor, a Facebook checkpoint or CAPTCHA. After three automatic attempts in 24 hours, the app directs you to sign in manually.

## If something goes wrong

| Symptom | What to do |
| --- | --- |
| Blank Facebook page | Follow the message to retry in a few minutes. If the app says it gave the phone a new connection, choose **Sign into Facebook on the phone** again. |
| Slow after startup | Allow a few moments for the phone to settle; do not create a second connection just because the first frames are slow. |
| Time is up or sign-in cancelled | Reopen sign-in and complete it within the new session's displayed time. |
| Wrong Facebook account | Sign in with the account linked to this profile. If it belongs to another existing profile, use the intended separate account instead. |
| **Saved password rejected** | Use **Replace password** when permitted, or sign in manually. |
| **Manual sign-in required** | Complete the two-factor, checkpoint or CAPTCHA instruction on the phone. Saved credentials do not bypass Facebook checks. |
| Phone entry may still be running | Wait while controls are blocked and the action is reconciled rather than sending overlapping input. |
| Could not import groups | Once connected, use **Sync now** in the profile's group management later. Sign-in and group import are separate steps. |
| Phone connected but publishing waits | Check identity choice, warmup, publishing pause and device setting. Safety does not use the cloud; video requires the browser. |
| Post may have landed / **Needs verification** | Check the Facebook group before publishing again to avoid a duplicate. |

## Sign out or remove a saved password

Choose **Disconnect from cloud phone** and read the confirmation. It signs Facebook out, wipes phone-browser data and deletes the saved password. Groups and campaigns remain; a post already being sent may finish. If Facebook has not yet signed in and only a password was saved, the password-only confirmation explains that it deletes the password without a phone session to disconnect.

## Related pages

- [Cloud phones overview](https://docs.lead-knight.com/en/cloud-phones/overview/)
- [Facebook identities](https://docs.lead-knight.com/en/channels/facebook-pages-and-identities/)
- [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/)
- [Posting settings](https://docs.lead-knight.com/en/extension/posting-presets/)