# Getting started with LeadKnight Create an account, complete setup, find your way around the app, and get help in the language you prefer. Canonical: https://docs.lead-knight.com/en/getting-started/overview/ ## Start here LeadKnight organizes your work inside workspaces. Your personal account can belong to more than one workspace, and your role and subscription access can differ between them. In the real-estate edition, Nadlanite, the workspace is presented as an office and campaigns are called properties. 1. [Create your account](https://docs.lead-knight.com/en/getting-started/create-account/), or [sign in and recover your password](https://docs.lead-knight.com/en/getting-started/sign-in/). 1. [Complete onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/). The steps adapt to your field, goals, membership and previous setup. 1. For the real-estate edition, [set up or join an office](https://docs.lead-knight.com/en/getting-started/real-estate-office/). If offered, [bring over your previous Nadlanite account](https://docs.lead-knight.com/en/getting-started/nadlanite-import/). 1. [Take an app tour](https://docs.lead-knight.com/en/getting-started/app-tour/), then [connect your publishing accounts](https://docs.lead-knight.com/en/channels/overview/) and [create a campaign](https://docs.lead-knight.com/en/campaigns/overview/). ## Everyday controls - [Language and light/dark appearance](https://docs.lead-knight.com/en/getting-started/language-and-appearance/): desktop header and phone account menu. - [Notifications](https://docs.lead-knight.com/en/getting-started/notifications/): read updates for your current workspace. - [Help, videos and documentation](https://docs.lead-knight.com/en/getting-started/help/): use the round question-mark control. - [Workspaces and your team](https://docs.lead-knight.com/en/team/overview/): switch workspaces, understand roles and accept invitations. - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/): understand seats, trials and your own bills. - [Your account](https://docs.lead-knight.com/en/account/overview/): profile, sign-in methods, referrals and feedback. ## What to expect The **Assistant** entry opens the conversation page. **Connections** is where you connect publishing accounts; creating an app account does not automatically connect social networks. Preparing content and publishing it are different actions: review the destination and final action before proceeding. Some features are enabled separately for each workspace. If an optional menu entry is absent, it may not be enabled for that workspace yet; changing your language does not unlock features. A role or subscription notice may also explain why an action is unavailable. For business settings and notification preferences, see [Settings](https://docs.lead-knight.com/en/settings/overview/). For common problems, see [Troubleshooting](https://docs.lead-knight.com/en/troubleshooting/overview/). --- # Create your account Register with Google or an email and password, accept the terms, and complete email confirmation when requested. Canonical: https://docs.lead-knight.com/en/getting-started/create-account/ ## What this does Registration creates your personal app account. Workspace setup and social-network connections come afterwards. An invitation can instead open a registration form that keeps the invitation as your destination. ## Before you start Use an email address you can access, or the Google account you want to use for future sign-ins. Read the **Terms of Service** and **Privacy Policy** linked next to the consent checkbox. You must accept them before either registration method can continue. ## Create the account 1. Open the sign-up page. The public page shows **Start your 10-day free trial**. If you already have an account, choose **Already have an account? Sign in** instead. 1. Select the checkbox accepting the **Terms of Service** and **Privacy Policy**. If it is missing, the form highlights it rather than completing registration. 1. Choose **Continue with Google**, then complete Google's account selection; or enter **Email** and **Password** in the form. 1. For email registration, complete the human-verification check if shown, then choose **Start free trial**. An invitation or embedded form may instead label the action **Create account**. 1. If **Check your email** appears, open the confirmation message and its link. The notice shows the destination email. If confirmation is not required, the app continues directly. 1. Continue to the setup flow or the invitation you opened. Follow [onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/) to create or join the correct workspace. ## Password and trial notes - The registration form requires at least eight characters and refuses passwords longer than 200 characters. Follow any stronger-password guidance shown by the service. - The public sign-up screen advertises a ten-day free trial with no payment during the trial. Creating credentials is not the same as activating a seat: review the actual plan, trial eligibility and payment terms in the seat dialog before confirming. See [Plans and billing](https://docs.lead-knight.com/en/billing/overview/). - Google sign-in does not connect a social publishing account. Those connections are separate. ## If something goes wrong | What you see | What it means and what to do | |---|---| | The consent checkbox is highlighted | Accept the linked terms and privacy policy, then retry your chosen method. | | No confirmation email | Check spam and promotions, verify the address displayed, and use sign-in if you already registered. The notice deliberately does not reveal whether an address already has an account. | | An expired confirmation link | Start sign-up again to request a fresh confirmation link. | | A human-verification error | Complete the check below the fields and submit again. | | Too many attempts | Wait before retrying; repeated submissions do not bypass the limit. | | Google sign-in does not start | Retry after checking your connection. Do not assume registration succeeded from this error. | ## Related pages - [Sign in or reset a password](https://docs.lead-knight.com/en/getting-started/sign-in/) - [Complete onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/) - [Accept a team invitation](https://docs.lead-knight.com/en/team/overview/) ## Create your LeadKnight account [Create your LeadKnight account](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/A1/leadknight-en-be44f6c8c982.mp4) 1. Creating your LeadKnight account takes about a minute, and your first 10 days are free. 2. First, tick the box to accept the Terms of Service and Privacy Policy. 3. You can sign up with your email and a password, then click Start free trial. 4. Or do it faster: click Continue with Google. 5. Pick your Google account. 6. Your account is ready, and LeadKnight opens a short setup. --- # Sign in or reset your password Use Google or your email and password to sign in, or request and complete a password reset safely. Canonical: https://docs.lead-knight.com/en/getting-started/sign-in/ ## Before you start Use the account you registered with. If you created the account through Google and have not added a password, use **Continue with Google**. Setting an app password later is separate from changing your Google password. ## Sign in 1. Open the login page. You see **Welcome back**. 1. Choose **Continue with Google** and complete the provider screen, or enter **Email** and **Password**. 1. Complete the human-verification check if shown and choose **Sign in**. The app resumes access to your workspace or asks you to finish setup. 1. If you entered through an invitation, continue with that invitation rather than creating an unrelated workspace. ## Reset a forgotten password 1. Choose **Forgot password?**, or open the password-reset page. The screen changes to **Reset your password**. 1. Enter your email and choose **Send reset link**. The confirmation explains that, if an account exists, you should look in your inbox or spam. It is not proof that this address is registered. 1. Open the latest reset email and its link. Choose **Continue** on the reset screen to open the password form. 1. Check which identity the form is for. Enter **New password** and **Confirm password**, following the displayed requirements: 8–200 characters including an uppercase letter, a lowercase letter and a number. 1. Choose **Save password**. If identity confirmation is requested, follow the email-code or authenticator instructions shown. 1. After the saved-password confirmation, choose **Back to sign in** and sign in with your email and new password. Saving the password does not silently sign you into a different account. ## Options and recovery rules - **Try another email** returns to the reset request if you used the wrong address. - **Use another link** leaves the current reset attempt so you can use the correct one. - A link that has expired or was already used requires **Send a new link**. - Google remains a separate sign-in option when it is connected. For managing sign-in methods after login, see [Your account](https://docs.lead-knight.com/en/account/overview/) and [Settings](https://docs.lead-knight.com/en/settings/overview/). ## If something goes wrong | Symptom | Next step | |---|---| | Incorrect email or password | Check the address and sign-in method; use reset rather than repeatedly guessing. | | Email not confirmed | Open the registration confirmation message first. | | No reset email | Check spam and the latest message; a recent request can be rate-limited. Wait before requesting another. | | Link cannot open because of a connection error | Check your connection and retry; a network failure is not the same as an expired link. | | Passwords do not match | Re-enter the same new password in both fields. | | Your signed-in identity changed | Sign in again as the intended account before changing a password. | ## Related pages - [Create an account](https://docs.lead-knight.com/en/getting-started/create-account/) - [Complete onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/) - [Your account](https://docs.lead-knight.com/en/account/overview/) ## Create your LeadKnight account [Create your LeadKnight account](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/A1/leadknight-en-be44f6c8c982.mp4) 1. Creating your LeadKnight account takes about a minute, and your first 10 days are free. 2. First, tick the box to accept the Terms of Service and Privacy Policy. 3. You can sign up with your email and a password, then click Start free trial. 4. Or do it faster: click Continue with Google. 5. Pick your Google account. 6. Your account is ready, and LeadKnight opens a short setup. --- # Complete your initial setup Understand every setup step, the owner and invitee paths, optional connections, and the final first-post or seat step. Canonical: https://docs.lead-knight.com/en/getting-started/onboarding/ ## What setup does The wizard asks only the questions that apply to your current membership. Creating your first workspace, creating another workspace, joining a team and joining as a viewer are different paths. Personal details already completed in another workspace may be omitted. ## Before you start Sign in to the intended personal account. Prepare the workspace or office name, a contact phone number and an email. A logo, photo and descriptions are optional. If joining an office, get its join code instead of creating a duplicate office. ## Owner setup, step by step 1. In **Field**, choose what you do. Choosing an industry advances the wizard; **My field isn't listed** lets you type your own field and choose **Continue**. Real estate uses the Nadlanite edition. 1. If a previous Nadlanite account offer appears, review it or choose **Not now**. This is conditional, not a mandatory step for every real-estate user. Follow [the migration guide](https://docs.lead-knight.com/en/getting-started/nadlanite-import/). 1. In **Goals**, select at least one goal. Choices cover social presence, leads, AI assistance and paid ads. Complete the question about how you heard about the app and any follow-up question shown. 1. In **Workspace**, enter a name. Adding a name reveals optional **Logo** and **What the business does** fields. These help prepare content. In the real-estate edition, **Office** asks how you work and can offer joining instead; see [office setup](https://docs.lead-knight.com/en/getting-started/real-estate-office/). 1. If **Previous subscription** appears after the office exists, complete or decline the relevant transfer flow. An earlier choice to use another Nadlanite email is verified here. 1. In **Accounts**, choose a network and complete its connection flow. Facebook groups use the extension or cloud-phone connection offered in that flow. **More** opens additional networks. Your connected accounts are shown for review. You can choose **I'll connect later** and confirm **Connect later**; preparing a post does not remove the need for a connected network before publishing. 1. If you chose the paid-ad goal, **Paid ads** offers ad-account connections. This step is optional. If paid ads are unavailable in this workspace, the screen says so and you can continue. 1. In **Assistant**, optionally connect **Google Calendar**, **Gmail** or **WhatsApp** where enabled. A disabled integration shows **Not available yet**. These are assistant connections, not substitutes for publishing-account connections. Gmail's setup text explains that sends require approval. 1. In **Details**, complete **Full name**, **Gender**, **Phone** and **Email**. Check any prefilled values. **Your photo** and **A sentence about you** are optional; the real-estate edition also offers a broker-license field. The preview reflects the details entered. 1. In **Publish**, choose the manual or AI creation path. Review the content, destinations and final action inside that creator. The seat dialog may appear before saving or publishing; read its plan and payment terms first. **Skip for now** is available on the initial choice screen. After successful completion, the app opens the relevant campaign/property or the app destination for the completed path. ## Joining members and viewers - Invited admins and members begin at **Welcome**, which names the workspace and role. If needed, they complete their own goals and details, then their connections, optional paid-ad connections, assistant connections and first post. They do not repeat the owner's office setup. - Viewers begin at **Welcome**, complete personal steps when needed, then **Seat**. They do not connect networks or publish. Once the seat is ready, their own confirmation opens the workspace. - When someone else pays for your seat, wait for it to become ready. Use **Check again** if needed. A ready-seat notice is not a publish command: press the relevant button yourself to continue. ## Navigation and rules You can return to a step already reached, but cannot jump ahead to an unreached step. If a required answer is missing, the wizard highlights it. If access requires a seat earlier, **Set up your seat to continue** explains why; activating the seat resumes the flow rather than starting a new workspace. ## If something goes wrong | Symptom | Cause and next step | |---|---| | Continue does not advance | Fill the highlighted required answer, including follow-up attribution or a valid phone/email. | | A phone is already in use | Check whether it belongs to your other account; resolve the conflict rather than inventing a number. | | Logo or photo could not be kept | Choose it again, or remove the optional image and continue without it. | | Waiting for an office | The join request needs the office's approval. Follow the waiting screen instead of creating another office. | | Seat is being set up for you | Wait for the payer, then check again and continue once ready. | | The post was saved but setup could not finish | Use **Retry** on that completion screen; do not create a second copy of the saved post. | ## Related pages - [Real-estate office setup](https://docs.lead-knight.com/en/getting-started/real-estate-office/) - [Previous Nadlanite account](https://docs.lead-knight.com/en/getting-started/nadlanite-import/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) - [Connections](https://docs.lead-knight.com/en/channels/overview/) - [App tour](https://docs.lead-knight.com/en/getting-started/app-tour/) ## Choose your field [Choose your field](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B1/leadknight-en-9c05c7c89b24.mp4) 1. The setup starts with one question: what do you do? 2. It's step one of a short setup. 3. Pick the field closest to your business. LeadKnight shapes its wording, content and networks around it. 4. Not on the list? Choose My field isn't listed and type it in. 5. Here we'll pick Real estate. 6. For real estate, the app switches to Nadlanite, our real-estate edition, and moves to the next step. ## Choose your onboarding goals [Choose your onboarding goals](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B2/nadlanite-en-2d8a8978ba79.mp4) 1. Choose what you want Nadlanite to help you achieve. 2. Select social presence for consistent posting. 3. Choose several goals if you like. Here, we also add the AI assistant. 4. Paid ads is another option. 5. Next, tell us how you heard about the app. 6. Choose the answer that applies to you. 7. Click Continue to set up your office. ## Create your workspace [Create your workspace](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B3/leadknight-en-6b27d6c93ecb.mp4) 1. Your workspace holds your accounts, content and team. 2. Give your workspace a name, usually your business name. 3. The business details are optional, but they help the AI write your first posts. 4. Add your logo to show it on the images and posts we create. 5. Describe what your business does in a sentence or two. 6. Click Continue to create your workspace. ## Connect networks during setup [Connect networks during setup](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B7/nadlanite-en-37c5baed93f2.mp4) 1. Choose which networks you want to use with Nadlanite. 2. Facebook groups use the browser extension. 3. Pages and other social networks connect through their own account authorization. 4. Explore connections shows the other available networks. 5. To finish setup first, click Skip. 6. You cannot publish until an account is connected. 7. Confirm Skip. You can connect later from Connections. ## Choose assistant connections [Choose assistant connections](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B8/nadlanite-en-350330fbcf48.mp4) 1. These optional connections let the assistant help with more of your work. 2. Google Calendar connects your schedule and meeting tools. 3. Gmail lets the assistant prepare email from your account, with approval before sending. 4. WhatsApp lets you talk to the assistant from your phone. 5. Connect now, or continue and set these up later. ## Add your contact details and preview [Add your contact details and preview](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B9/nadlanite-en-52c8ca6a8c13.mp4) 1. Add the contact details your account needs. Profile extras are optional. 2. Enter your full name. 3. Choose your gender. 4. Add a phone number, including the country code when needed. 5. Check that your contact email is correct. 6. An optional description helps personalize your content. 7. Click Preview to see how your identity will appear. 8. Review the preview before you continue. 9. Close the preview, then click Continue. ## Choose how to create your first property content [Choose how to create your first property content](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B10/nadlanite-en-e7ca766c66fe.mp4) 1. Choose how you want to create your first property content. 2. Choose Me to write the post and select your media yourself. 3. Choose The AI for help preparing the content and schedule. 4. You can also skip this and create content later. 5. Here, we choose The AI and start with the property details. ## Choose your plan and start the free trial [Choose your plan and start the free trial](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P8/nadlanite-en-eca015747cea.mp4) 1. Before your seat starts, you choose a plan. 2. Every plan starts with ten days free. Nothing is charged today, and you can cancel during the trial. 3. Monthly has no commitment. 4. Quarterly commits for three months at a lower monthly price. 5. Yearly has the lowest monthly price. 6. All plans include the same features. 7. Open the questions below for answers about the trial, cancelling, and invoices. 8. When you are ready, click Start free on the plan you want, and add your card on the secure payment page. --- # Set up or join a real-estate office Choose independent work, create an office with agents, or request to join an existing office during Nadlanite setup. Canonical: https://docs.lead-knight.com/en/getting-started/real-estate-office/ ## What this is for The **Office** setup step adapts to whether you work independently, own an office or work inside an existing one. Joining another office does not make you its owner. This page applies to the real-estate edition, Nadlanite. ## Before you start Choose real estate in **Field** and complete **Goals**. If you are an agent in an existing office, ask its owner or administrator for the office join code. Creating a new office is a different action from requesting membership in one. ## Create your own office 1. At **How do you work today?**, choose **On my own** if you are independent, or **I own an office** if you have a team. The next fields reflect your choice. 1. For an office with a team, answer **How many agents do you have today?**. This describes your team; it is not the same as purchasing that number of seats. 1. Fill **What should we call your office?**. A name is required to continue. Optional office details appear below it. 1. Add a **Logo** if wanted, then describe **What makes your office stand out?**. The description helps prepare content; it does not publish anything by itself. 1. Optionally add service cities under **Which cities does your office serve? (optional)**. Type a city and choose **Add**. Each city must be unique and 1–60 characters long; the UI allows up to 20 cities. Remove a city if needed before adding another. 1. Choose **Continue**. The wizard creates or updates the office and moves to its next applicable step. Continue with connections, personal details and first content as described in [onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/). ## Join an existing office instead 1. During first-workspace setup, choose **An agent in an office** when that choice is offered. 1. Enter the office's join code in the join form and choose **Continue**. A valid code sends a membership request; it does not immediately open the office. 1. Check the office name on the waiting screen. Wait for approval, or follow the screen's cancellation option if you requested the wrong office. 1. After approval, continue into that office. The onboarding path uses your assigned role and keeps applicable personal answers. You are not asked to set up the owner's office again. The first-workspace path offers joining by code. When deliberately creating an additional workspace, use the workspace switcher's joining action instead of assuming this owner-setup flow will join an office. ## Rules and permissions Owners set up the office in this wizard. Invited members, including admins, have a personal onboarding path rather than repeating the owner's setup. Office details can be read-only when you do not have permission to change them. Your personal photo and broker-license field belong to **Details**, not the office logo section. ## If something goes wrong | Symptom | What to do | |---|---| | Invalid or unavailable join code | Ask the office to confirm or replace its code; do not create a duplicate office as a workaround. | | Still waiting | Approval has not been granted yet. Check with the office owner or administrator. | | A service city is refused | Check uniqueness, length and the displayed city limit. | | Logo upload fails | Select the file again or remove the optional logo before continuing. | | Office fields are read-only | You are not in the owner-setup path or lack permission; ask an authorized office member. | ## Related pages - [All onboarding steps](https://docs.lead-knight.com/en/getting-started/onboarding/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) - [Bring over a previous Nadlanite account](https://docs.lead-knight.com/en/getting-started/nadlanite-import/) ## Set up your real-estate office [Set up your real-estate office](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B4/nadlanite-en-0863ff5f1d4e.mp4) 1. Choose whether you work alone, in an existing office, or run an office. 2. For an office with a team, choose I own an office. 3. Select your current office size. 4. Enter your office name. 5. Add a short description to help tailor your content. 6. You can also add your logo and service cities. 7. Click Continue to create the office. ## Join an existing office [Join an existing office](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/B5/nadlanite-en-9ebe7b5c0521.mp4) 1. Already part of an office? You can request to join it. 2. Choose An agent in an office. 3. Ask your office owner or admin for the ten-character code on their Team page. 4. If you do not have a code, this option lets you choose another setup path. 5. With a valid code, Continue sends a join request. Your office must approve it. --- # Bring over your previous Nadlanite account Review an offered Nadlanite transfer, verify another email when needed, understand subscription consent, and follow import progress. Canonical: https://docs.lead-knight.com/en/getting-started/nadlanite-import/ ## What this does When an eligible offer is available in the real-estate edition, setup can bring over a previous Nadlanite account or subscription. Read the offer carefully: an account import and a subscription-only transfer are not the same. The screen describes which is available for you. ## Before you start Sign in with the intended account. Have access to the email used in the old Nadlanite system, even if it differs from your current email. Check any existing renewal arrangement before accepting or declining a transfer. ## Review and accept the offer 1. After choosing real estate, review **Bring over my Nadlanite account** if offered. An early offer can fill unanswered office and personal details; the account is transferred into the office after that office exists. 1. Check the account match, counts and subscription details displayed. If the old account uses another address, choose **My Nadlanite account uses another email**. An early selection continues to verification after office creation. 1. When the email form appears, enter **Nadlanite email address** and choose **Send verification code**. Enter the **6-digit verification code** and choose **Verify email**. Use **Resend code** if necessary. 1. Read the actual subscription consent, price information and first-charge date shown. Monthly and yearly transfers have different terms. Accept the required consent only if you agree. Do not treat a prefilled logo or account lookup as confirmation that billing transferred. 1. If data import is offered, review **Resume posting automatically**. Leaving it selected requests continuation of eligible active properties after the required Facebook connection and group matching. Clear it if you do not want that automatic continuation. 1. Choose **Bring over my account**, or **Bring my subscription** for a subscription-only offer. Wait for the result. If no eligible subscription exists, the offer can explain that only data moves. 1. For an account import, follow **Import progress** and **What was brought over**. You may leave the screen while import continues; return to billing for **View import progress and summary**. ## What moves and what still needs attention An account-import offer describes properties, photos and videos, contacts, tasks and posting settings. The import summary distinguishes created, updated, kept, skipped and failed items. A completed import can still have skipped or failed items; inspect those details rather than assuming every record arrived. Facebook groups are matched when Facebook is connected. Posting can wait for Facebook, group loading or a choice of publishing profile/Page. Import completion is not proof that a post has reached Facebook. A subscription-only offer explicitly says the properties and contacts remain in the old system for now. ## Declining or skipping **Not now** can show a warning that the old Nadlanite subscription keeps renewing. **Back to the transfer** returns to the offer; **Continue without moving** leaves it. If you keep an old subscription, cancel it with the old provider if necessary to avoid double billing. A data-only import does not automatically cancel an old renewal that was not transferred. ## If something goes wrong | Symptom | Next step | |---|---| | No offer appears | The flow is conditional; do not assume all accounts are eligible. Continue normal setup. | | Another email must be verified | Use the old account's address and the latest code, not a different person's account. | | Import completed with failures | Inspect skipped items and reasons, including unavailable media or invalid contact details. | | Import could not complete | Use **Try importing again**. The interface says your existing edits will be kept. | | Imported properties are waiting to post | Connect Facebook, let groups load and choose the posting identity if requested. | | Billing has not been transferred | Review the consent and result; a saved account claim alone does not mean the subscription moved. | ## Related pages - [Office setup](https://docs.lead-knight.com/en/getting-started/real-estate-office/) - [All onboarding steps](https://docs.lead-knight.com/en/getting-started/onboarding/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) - [Facebook group connections](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) --- # Find your way around the app Tour the desktop sidebar, phone navigation, main work areas, account menu and workspace switcher. Canonical: https://docs.lead-knight.com/en/getting-started/app-tour/ ## Before you start Finish the setup required for your membership and open the app in the intended workspace. The workspace name in the switcher tells you where you are working. This tour explains navigation; it does not publish content or change your plan. To start the interactive version, open the question-mark help panel on **Assistant**, select the app-tour video for your edition, and choose **Show me**. The video closes and guidance points at the real navigation controls. Follow the tour prompts yourself; it does not click or submit for you. The steps below also work as a written tour without a video. ## Take the tour 1. Open **Assistant**. Although its address ends in `/dashboard`, this is the assistant conversation, not a separate analytics dashboard. The main area shows the current page; the header names the section. 1. On a desktop, use the sidebar to choose a work area. The selected entry is highlighted and the main area changes to that page. In Nadlanite, **Properties** replaces **Campaigns**. 1. On a phone, use the bottom navigation: **Assistant**, **Campaigns** or **Properties**, the central plus button, **Calendar**, and **More**. The plus opens creation. **More** opens the remaining sections and the workspace switcher. The bar steps aside during creation and while typing in chat. 1. Open the account avatar in the header. **My profile** opens personal details; **My billing** opens bills and seats you pay for across workspaces. The menu also contains sign-out. On smaller screens, language and theme controls are here too. 1. Open **Switch workspace** in the desktop sidebar or phone's **More** panel. The current workspace is marked. Choose another membership only when you want to work in that workspace; each has its own role and data. 1. Use the notifications bell for updates and the round question-mark control for guidance. Read [Help and videos](https://docs.lead-knight.com/en/getting-started/help/) for its current options. ## Main work areas | Menu entry | What it is for | |---|---| | **Assistant** | Conversational assistance. See [AI assistant](https://docs.lead-knight.com/en/assistant/overview/). | | **Campaigns** / **Properties** | Prepare and manage your content. See [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/). | | **Scheduled content** | Calendar view of scheduled work. See [Calendar](https://docs.lead-knight.com/en/calendar/overview/). | | **Photo studio** / **Video Studio** | Image and video work. See [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/) and [Video studio](https://docs.lead-knight.com/en/video-studio/overview/). | | **Analytics** | Reporting. See [Analytics](https://docs.lead-knight.com/en/analytics/overview/). | | **Chats** | Conversations. See [Inbox](https://docs.lead-knight.com/en/inbox/overview/). | | **Contacts** / **Audiences** | Manage contacts and groups of people. See [Contacts](https://docs.lead-knight.com/en/contacts/overview/) and [Audiences](https://docs.lead-knight.com/en/audiences/overview/). | | **Sites** | Website work when enabled. See [Sites](https://docs.lead-knight.com/en/sites/overview/). | | **Connections** | Publishing accounts and destinations. See [Connections](https://docs.lead-knight.com/en/channels/overview/). | | **Team** | Members, roles and seat status. See [Team](https://docs.lead-knight.com/en/team/overview/). | | **Earn** | Affiliate program when enabled. See [Your account](https://docs.lead-knight.com/en/account/overview/). | | **Settings** | Workspace and account preferences. See [Settings](https://docs.lead-knight.com/en/settings/overview/). | ## Availability and safe navigation If you don't see **Sites**, **Video Studio** or **Earn** in the menu, it isn't enabled for your workspace yet. A page being visible does not mean every action on it is permitted for your role or seat. Opening navigation entries does not itself start a campaign or spend an advertising budget. ## If something goes wrong - Can't find the sidebar on your phone: use **More** in the bottom bar. - Theme or language buttons are missing from the header: open **Account** on smaller screens. - The content or role seems wrong: check the workspace name before editing anything. - A seat notice blocks progress: read the notice and [billing overview](https://docs.lead-knight.com/en/billing/overview/), rather than making a duplicate workspace. ## Related pages - [Language and appearance](https://docs.lead-knight.com/en/getting-started/language-and-appearance/) - [Notifications](https://docs.lead-knight.com/en/getting-started/notifications/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) ## Tour of the app (general business) [Tour of the app (general business)](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/C1-GEN/leadknight-en-df3adef3b6af.mp4) 1. This is your home. Assistant is where you ask the AI to write, schedule and manage your work. 2. New campaign starts a new campaign with AI or on your own. 3. Campaigns lists all your campaigns and their posts. 4. Scheduled content shows what goes out and when. 5. Photo studio edits your images. 6. Chats collects your conversations in one inbox. 7. Contacts is your CRM for leads and customers. 8. Sites builds landing pages. 9. Connections links your social accounts and the Chrome extension. 10. Team and Settings manage your people and preferences. 11. Switch between workspaces here. 12. Up top: notifications, language, theme, and your account. ## Tour of the app (real estate) [Tour of the app (real estate)](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/C1-RE/nadlanite-en-beb095f63edc.mp4) 1. This is your home. Assistant is where you ask the AI to write, schedule and manage your work. 2. New property starts a new property campaign. 3. Properties lists your property campaigns and their posts. 4. Scheduled content shows what goes out and when. 5. Photo studio edits your images. 6. Chats collects your conversations in one inbox. 7. Contacts is your CRM for buyers and sellers. 8. Sites builds landing pages for your properties. 9. Connections links your social accounts and the Chrome extension. 10. Team and Settings manage your people and preferences. 11. Switch between workspaces here. 12. Up top: notifications, language, theme, and your account. --- # Change language and light or dark mode Switch between English and Hebrew and change the app appearance from the header or phone account menu. Canonical: https://docs.lead-knight.com/en/getting-started/language-and-appearance/ ## What this changes The language control changes the interface between English and Hebrew. Hebrew uses right-to-left layout. The theme control changes the app's light/dark appearance. Neither control translates a post you have written, changes your workspace membership or connects an account. ## Before you start Open an app page. On a wide screen, look at the header; on a phone or smaller screen, open the account avatar. The language button names the language you will switch to, not the language currently in use. ## On a desktop 1. In the header, choose **עברית** to switch an English interface to Hebrew. The labels change and the layout becomes right-to-left. 1. In Hebrew, choose **English** to return to English. The layout returns to left-to-right. 1. Choose the sun/moon button, named **Theme**, to switch appearance. When dark mode is active it offers the sun icon; when light mode is active it offers the moon icon. ## On a phone 1. Open **Account** using your avatar in the header. Its menu contains personal account actions and the compact-screen preferences. 1. Choose **עברית** or **English** to switch language. Reopen the menu if you also want to change appearance. 1. Choose **Dark mode** or **Light mode**. The action names the mode you will turn on. ## Options and scope There are two interface languages and light/dark switching in these quick controls. Additional account preferences are described in [Settings](https://docs.lead-knight.com/en/settings/overview/). The edition remains the edition of the current workspace: switching to Hebrew does not change LeadKnight into Nadlanite, or vice versa. ## If something goes wrong - No separate language or theme buttons: they move into **Account** on smaller screens. - Can't read the current interface: look for **English** or **עברית**, written in the target language. - Existing post text stays in its original language: this control changes interface labels, not content. Edit the post separately. - A feature is still absent after switching language: availability is workspace-specific, not language-specific. ## Related pages - [App tour](https://docs.lead-knight.com/en/getting-started/app-tour/) - [Help and videos](https://docs.lead-knight.com/en/getting-started/help/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) ## Switch language and light/dark mode [Switch language and light/dark mode](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/C2/nadlanite-en-81159d0256c4.mp4) 1. To switch language, use this button in the top bar. 2. The whole app switches to Hebrew, right to left. 3. Click again to switch back. 4. The theme button switches to dark mode. 5. Click again for light mode. --- # Read your notifications Open the notifications bell, follow an update to its page, and mark notifications as read in the current workspace. Canonical: https://docs.lead-knight.com/en/getting-started/notifications/ ## What the bell shows The header bell opens notifications for the current workspace. An unread-count badge indicates regular unread notifications; a welcome notice can have its own dot. A notification can contain a link to the relevant page, but not every item needs a destination. ## Before you start Check your workspace in the switcher. If you are looking for updates from another workspace, switch to it first. Notification delivery preferences are separate from reading the bell; see [Settings](https://docs.lead-knight.com/en/settings/overview/). ## Read and follow an update 1. Choose the bell labelled **Notifications** in the header. A list opens with the newest items first. 1. Read the item and its time. Opening the panel acknowledges unread welcome notices; regular items remain available to open individually. 1. Choose an item. The app marks it read and, if it contains a link, opens the related page. 1. To clear the remaining unread state together, choose **Mark all read**. The list refreshes after the action. 1. Close the panel to return to your current task if you do not want to follow a link. ## Options and limits **Mark all read** changes the read state; it does not delete the underlying campaign, task or notification event. The bell is not a guarantee that a social-network post was delivered: open the relevant result page to inspect the actual status. A welcome item can include privacy and terms links rather than a work item. ## If something goes wrong | Symptom | What to do | |---|---| | **No notifications yet** | There are no items to show for this workspace; check you are in the intended workspace. | | **Could not load notifications** | Check your connection and try opening the bell again. Do not assume an empty or failed load means the underlying task succeeded. | | An item opens but still looks unread | Navigation can succeed even if marking it read fails. Reopen the list and retry the read action. | | Mark all read does not update | A failed request leaves the read state unchanged; retry after checking connectivity. | | Email or WhatsApp delivery is not as expected | Review notification preferences in Settings; the bell and external delivery are different surfaces. | ## Related pages - [Settings and notification preferences](https://docs.lead-knight.com/en/settings/overview/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) - [App tour](https://docs.lead-knight.com/en/getting-started/app-tour/) ## Read your notifications [Read your notifications](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/C3/leadknight-en-d2cd86d97017.mp4) 1. The bell in the top bar collects updates for this workspace. A red dot means something new. 2. Click it to open your notifications. 3. The newest ones appear first. 4. Click a notification or its links to go straight to the right place. 5. Press Escape or click outside to close. --- # Find help, videos and documentation Use the round question-mark help control for page guides, a searchable video library and documentation. Canonical: https://docs.lead-knight.com/en/getting-started/help/ ## What help offers The round **?** control opens **Guides for this page**. The menu offers available recordings for your current page or onboarding step, plus **Everywhere in the app** guides. Selection prefers a recording in your interface language and edition. If an applicable guide has only another edition's recording in your language, it can be shown with a note identifying that edition. The help panel also provides **Video library** and **Docs** actions. A written guide can exist even when no matching recording exists. ## Before you start Open the page where you need help and check the interface language and workspace. The help control depends on available guide content; it may not be shown before the app knows your edition. Do not expect every action to have a recording. ## Watch a guide for the current page 1. Choose the round question mark. The **Guides for this page** panel opens. 1. Pick the topic that matches your task. The row shows the title and duration. 1. The guide opens with a video player and written steps. Read the steps while watching; the video is an explanation, not an action performed on your account. 1. Close the guide and perform the steps in the app yourself. Review any real publish, payment or send confirmation before accepting it. For guides with an interactive tour, **Show me** closes the video dialog and starts guidance over the app's real controls. It does not click or submit for you. Not every video has a matching tour. ## Search the video library 1. Open the help panel and choose **Video library**. A dialog lists available recordings grouped by product area. 1. Enter a topic in **Search videos**. Search uses guide titles and summaries, not an analysis of the video's pictures or audio. 1. Choose a result to open its video and steps. A recording can be marked **Full walkthrough** or as a part of a series; parts appear together in sequence. 1. If **No videos found** appears, shorten the search or try the feature's name in the current interface language. An empty search result is not proof that the feature itself is unavailable. ## Open written documentation In the help panel, choose **Docs**. Documentation opens in a new tab using the current app page and language to look up a relevant article. You can also begin with [Getting started](https://docs.lead-knight.com/en/getting-started/overview/) and follow the links for the area you need. On a phone, **More** also provides the guides entry. If the compact guides sheet does not show the library or documentation icons, use the round help panel where available or browse the documentation site directly; the two entry points need not show identical header actions. ## If something goes wrong - No page-specific video: use the library or written documentation. Not every page has a recording. - Wrong language or edition: check the language and workspace before selecting a guide again. - A video does not play: check connectivity and use the written steps rather than assuming the action ran. - Documentation did not open: check whether the browser blocked the new tab. - Video instructions and your permissions differ: follow the live screen's role, seat and confirmation requirements; a recording does not grant access. ## Related pages - [App tour](https://docs.lead-knight.com/en/getting-started/app-tour/) - [Change language](https://docs.lead-knight.com/en/getting-started/language-and-appearance/) - [Troubleshooting](https://docs.lead-knight.com/en/troubleshooting/overview/) --- # Your AI assistant Use the assistant to work with content, campaigns, contacts and connected services, with review and approval for sensitive actions. Canonical: https://docs.lead-knight.com/en/assistant/overview/ ## Start with the Assistant Choose **Assistant** in the app to open the chat page. Its address is `/dashboard`, but this is the assistant conversation, not the analytics dashboard. You can describe a task in ordinary language, give the assistant context and review what it proposes. The assistant works with tools connected to your workspace. A capability below is not a promise that every workspace has the relevant feature, account connection or permission. Ask for the specific outcome; if a connection or approval is missing, resolve that requirement rather than assuming the action happened. ## What you can ask it to do | Area | Examples of supported work | | --- | --- | | Content and campaigns | Draft and improve post copy, save drafts, create or update campaigns, inspect schedules and posting activity, pause or resume campaigns and request publishing. | | Destinations and Facebook groups | Find destinations and eligible groups, inspect group folders and prepare content for selected targets. Tell it exactly which account and destination you mean. | | Images and video | Inspect supported uploaded media, generate or edit images, combine images and work with video creation, editing and rendering when available. Media tasks can consume the relevant AI allowance. | | Contacts and tasks | Find and update contacts, log communications, create or manage tasks, record meeting outcomes and request CRM briefings. | | Calendar and Gmail | Find calendar events and free time, prepare events and invitations, or send an email through a connected Gmail account. These require the relevant connection and permissions. This calendar integration is distinct from the app's scheduled-content board. | | Research | Search the web, read public pages and carry out research to help with a content task. Outside content is not automatically a trusted instruction. | | Business and personal context | Recall saved rules and facts, search earlier conversations, read or update profile details and request workspace branding changes. | | Sites and paid ads | Work with site drafts and ad drafts, inspect results and request publication or an ad launch where enabled. Paid-ad launch still needs the target account owner's approval. | | Guides | Find a recorded product guide from your description and show it with written steps. | In Nadlanite, relevant real-estate tools also cover listings and matching buyers with listings. Do not assume those tools exist in a general-purpose workspace. ## Read the assistant guides - [Chat and give a task](https://docs.lead-knight.com/en/assistant/chat/): write a clear request, attach material and understand usage notices. - [Return to a past chat](https://docs.lead-knight.com/en/assistant/past-chats/): continue a web conversation or manage archived chats. - [Approvals and automatic publishing](https://docs.lead-knight.com/en/assistant/approvals/): review sensitive actions and understand what the publishing switch actually changes. - [Memory and writing style](https://docs.lead-knight.com/en/assistant/memory-and-writing-style/): review remembered facts, learned information and writing preferences. - [Get a video guide in chat](https://docs.lead-knight.com/en/assistant/video-guides/): ask for a matching recording and read the accompanying steps. ## Approval is not the same as completion Sensitive actions can pause for approval, including publishing, sending email, external calendar invitations, deleting calendar events and other operation-specific changes. Read the action and destination before selecting **Approve**. **Reject** declines the request. An expired request is not an approval. A draft, a plan or an approval card does not prove that content was published or a message was sent. Check the assistant's result and the relevant campaign, calendar or connected service. [Approval settings](https://docs.lead-knight.com/en/assistant/approvals/) can allow publishing without asking, but are not an unrestricted switch for every action. ## Assistant on WhatsApp When available, connect **Assistant on WhatsApp** from **Connections**. The connection flow provides a code to send in WhatsApp. Follow the code and expiry shown there; see [Connections](https://docs.lead-knight.com/en/channels/overview/). WhatsApp has its own conversation. In the app, the WhatsApp view is read-only and shows **Read this WhatsApp conversation here.** Approve or reject WhatsApp requests in WhatsApp, not in the read-only web view. Use **Web chat** to return to the web conversation. ## Usage notices If **Assistant usage limit reached** appears, the current reply can finish but new requests pause. The notice identifies the affected daily or three-hour token or outbound-message budget and shows when requests can resume when known. Use **Refresh usage** to check again. No fixed allowance is promised here: follow the value and availability shown for your account. ## Related areas [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/), [Contacts](https://docs.lead-knight.com/en/contacts/overview/), [Scheduled content](https://docs.lead-knight.com/en/calendar/overview/), [Settings](https://docs.lead-knight.com/en/settings/overview/) and [Analytics](https://docs.lead-knight.com/en/analytics/overview/) remain available as dedicated screens for inspecting the result of your work. ## Chat with your AI assistant [Chat with your AI assistant](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M1/nadlanite-en-e4d10f3dda58.mp4) 1. Your assistant lives on the home screen. Type what you need here. 2. Ask a question or give it a task, in your own words. 3. Then click Send. 4. The assistant answers in the conversation. 5. Start a separate conversation with New chat. 6. Past chats opens your earlier conversations. ## Go back to a past chat [Go back to a past chat](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M2/nadlanite-en-1e5e3cbe62b5.mp4) 1. Your conversations with the assistant are saved. Click Past chats. 2. Each chat shows its first message and when it started. 3. Archive hides a chat you no longer need. It doesn’t erase what the assistant remembers. 4. Click Continue to reopen a chat. 5. The chat opens where you left off. 6. To start fresh, click New chat. ## Assistant settings: memory, writing style and approvals [Assistant settings: memory, writing style and approvals](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M4/nadlanite-en-348904e0695c.mp4) 1. In Settings, the Assistant section shows what the assistant has learned and remembers about you. 2. To shape how it writes for you, click Add preference. 3. Describe your style in a few words, and save. 4. It now writes in your style, for you only. 5. Approvals decide whether it publishes on its own. Off means every publish waits for you. 6. Once WhatsApp is connected, it can also send reminders and a morning briefing. --- # Chat with the assistant and give it a task Start a conversation, provide a clear task, attach supporting files and understand replies, approvals and usage notices. Canonical: https://docs.lead-knight.com/en/assistant/chat/ ## What this is for Use **Assistant** to ask a question or carry out work in the current workspace. A conversation can move from planning to drafting and, when permissions and approvals allow, to an actual action. Make clear whether you want advice, a draft or execution. ## Before you start - Check your workspace and connect any account the task requires. - Decide which campaign, account, destination or contact you mean. A name and a clear distinguishing detail are more useful than “that one.” - For anything sent outside the app, prepare the intended recipients or destination and timing. Review the final proposal before approving. ## Send your first task 1. Choose **Assistant**. A new conversation shows **Start a conversation**; an existing conversation shows the transcript and **Message the assistant…**. 2. Type your request. For example: “Draft a short post about our consultation service for Instagram. Do not publish it.” This is an example request, not a fixed command you must copy. 3. Add facts or constraints that matter: audience, language, source material, desired length and whether the result should remain a draft. 4. Select **Send**, or press Enter. Shift+Enter adds a new line instead of sending. 5. Wait while the assistant works. Read the response and any request for clarification before submitting the next instruction. 6. If an approval card appears, inspect its content, targets and timing. Follow [Approvals](https://docs.lead-knight.com/en/assistant/approvals/) rather than treating the proposal as a completed action. 7. Check the final result in the relevant campaign, contact or connected service when the task changes something. You can prepare a follow-up while a reply is in progress, but sending may remain unavailable until the current operation finishes. A disabled send control is not a reason to repeat the request in another chat. ## Attach supporting files 1. Select **Attach a file** and choose files from your device. 2. Check the filenames and previews. Wait until **Uploading…** finishes; sending is blocked while a selected upload is still in progress. 3. Explain what you want the assistant to do with the material, then send the message. 4. Remove a file using its removal control if it is wrong or failed. A failed file is not a successfully attached source. The picker accepts JPEG, PNG, WebP, GIF and AVIF images, MP4 video, MPEG/WAV/OGG audio and PDF. AVIF is converted before upload. There are up to 25 files per message. File-size or readability errors can still prevent an upload; follow the error shown instead of assuming every file of an accepted type will work. Attachments supplied to the assistant are not automatically a valid social-media post attachment. Ask for the intended task and review the resulting post or media separately. ## Give a useful instruction | Include | Why it matters | | --- | --- | | The outcome | “Write a draft” and “publish this” are different requests. | | The exact target | Account, campaign, group, board, contact or recipient details prevent ambiguity. | | The source facts | Supply what is true about your business; do not ask the assistant to invent claims. | | Timing | Give the intended date and time, and check the workspace time zone in [Settings](https://docs.lead-knight.com/en/settings/overview/). | | Review boundaries | Say what must remain a draft or wait for your review. | For reusable facts and preferences, use [Memory and writing style](https://docs.lead-knight.com/en/assistant/memory-and-writing-style/) rather than retyping everything in each task. ## Usage notices **Assistant usage limit reached** pauses new requests while allowing the current reply to finish. The notice distinguishes daily and three-hour token budgets from daily and three-hour outbound-message budgets. It shows the next availability time when known. Use **Refresh usage** if the notice says availability is being checked or you want an updated status. A refresh failure does not mean the limit has disappeared. Starting **New chat** is for a fresh conversation, not a way around an allowance. ## WhatsApp conversations A WhatsApp conversation is separate from the web chat. If you open it in the app, it is read-only; continue messaging and approve or reject actions in WhatsApp. Select **Web chat** to return to the web composer. Connection setup is on [Connections](https://docs.lead-knight.com/en/channels/overview/). ## If something goes wrong - A file is too large, unreadable or fails to upload: remove it and choose a usable copy. Keep the task text; do not assume the assistant received that file. - **Send** is unavailable: wait for uploads or the current operation, check that your message is not empty and check for a usage notice. - The assistant is temporarily unavailable: use **Retry** when offered. Before repeating a publishing or sending request, inspect whether the previous action already completed. - The page says the current chat changed elsewhere: your unsent message is kept. Read the newly displayed conversation before sending it. - The assistant asks for a specific account or destination: give that detail rather than approving an ambiguous target. ## Related pages - [Assistant overview](https://docs.lead-knight.com/en/assistant/overview/). - [Past chats](https://docs.lead-knight.com/en/assistant/past-chats/). - [Approvals](https://docs.lead-knight.com/en/assistant/approvals/). - [Video guides in chat](https://docs.lead-knight.com/en/assistant/video-guides/). ## Chat with your AI assistant [Chat with your AI assistant](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M1/nadlanite-en-e4d10f3dda58.mp4) 1. Your assistant lives on the home screen. Type what you need here. 2. Ask a question or give it a task, in your own words. 3. Then click Send. 4. The assistant answers in the conversation. 5. Start a separate conversation with New chat. 6. Past chats opens your earlier conversations. --- # Return to a past chat Find an earlier assistant conversation, continue a web chat and manage the archive without confusing it with assistant memory. Canonical: https://docs.lead-knight.com/en/assistant/past-chats/ ## What this is for **Past chats** lets you return to conversations in the current workspace. Web conversations can be continued; WhatsApp conversations are read-only in the app. **Archive** hides a chat from the main list without erasing the assistant's memory. ## Before you start Check the current workspace and review any unsent message in the composer. Continuing another chat changes which conversation is current. Do not assume a message written for one conversation is appropriate in another. Wait for an in-progress reply or approval decision to finish before switching. The app disables continuation while a conflicting chat operation is running. ## Continue a web conversation 1. Open **Assistant**. 2. Select **Past chats** from the home view or conversation header. A side panel opens and loads the conversation list. 3. Identify the chat using its title, activity time and channel label. **Current** marks the current web chat. Some conversations may be **Untitled**. 4. For a web chat in the main list, select **Continue**. The chosen chat becomes the active conversation and the panel closes. 5. Read the restored messages before sending your next request. A pending proposal is not proof that its action was completed. If the list has another page, **Show more** loads additional chats. **No past chats yet.** is the empty-list state, not an error. The home view may also show recent chats. Selecting one opens the relevant web conversation or the read-only WhatsApp detail, depending on its channel. ## Read a WhatsApp conversation 1. Open **Past chats** and select a WhatsApp chat's title. 2. Read the detail view, marked **This conversation is read-only.** 3. Use **Back** to return to the list, or **Done** to close the panel. There is no web composer or web approval action for this history view. Continue the exchange and approve or reject requests in WhatsApp itself. ## Archive a completed chat 1. Find a closed conversation that is not the current chat. 2. Select **Archive** when the action is offered. The row leaves the main list. 3. Expand the **Archive** section to find archived conversations. The archive action is not offered for every row: a current or still-open conversation is not eligible for the same action. Do not treat a missing button as proof that the chat was already erased. ## Restore an archived conversation 1. Open **Past chats** and expand **Archive**. 2. Select the archived chat's title. The detail opens read-only. 3. Select **Restore**. The chat leaves the archive and returns to the main list. 4. For a restored web chat, use **Continue** to make it the active conversation. Restoring alone does not automatically resume it. > **Important:** Archiving only hides the chat. It does not erase the assistant's remembered facts, shared rules or learned writing preferences. Manage those separately in [Memory and writing style](https://docs.lead-knight.com/en/assistant/memory-and-writing-style/). ## Start a separate conversation From an active web conversation, select **New chat**. The app must successfully start the new conversation before replacing the old view. Starting a new chat is not the same as archiving, deleting memory or increasing your usage allowance. ## If something goes wrong - The list fails to load: select **Retry**. Existing conversations are not proven missing by a load error. - A chat fails to open: the app reports that the current conversation is unchanged. Retry rather than assuming the switch happened. - **Continue** is disabled: wait for streaming, a new-chat request, another switch or an approval decision to finish. - Archiving or restoring fails: the panel shows the error. Retry the intended action; do not infer a successful move from a click alone. - **New chat** fails: the old conversation stays on screen. Do not send sensitive new-context instructions assuming they will enter a different chat. - You cannot find an older exchange: check **Archive**, load more rows and confirm the workspace. You can also ask the assistant to search earlier conversations by topic or date. ## Related pages - [Assistant overview](https://docs.lead-knight.com/en/assistant/overview/). - [Chat and give a task](https://docs.lead-knight.com/en/assistant/chat/). - [Memory and writing style](https://docs.lead-knight.com/en/assistant/memory-and-writing-style/). ## Go back to a past chat [Go back to a past chat](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M2/nadlanite-en-1e5e3cbe62b5.mp4) 1. Your conversations with the assistant are saved. Click Past chats. 2. Each chat shows its first message and when it started. 3. Archive hides a chat you no longer need. It doesn’t erase what the assistant remembers. 4. Click Continue to reopen a chat. 5. The chat opens where you left off. 6. To start fresh, click New chat. --- # Approvals and automatic publishing Review sensitive assistant actions and choose whether publishing can proceed without asking, including safeguards after outside content. Canonical: https://docs.lead-knight.com/en/assistant/approvals/ ## What approval means The assistant can prepare an action without immediately carrying it out. Sensitive actions can pause for approval: publishing, sending email, inviting external calendar guests, deleting calendar events and other operation-specific changes. Workspace branding changes always need approval. Paid-ad launch needs the target account owner's approval. A request to draft something is not a request to send it. An approval card is a proposal, not a completed publication or message. ## Before you approve Check the action, exact target, content and timing. A publishing plan can include the campaign, text, media and one row per network with the account, destinations and schedule. Other cards show the relevant summary and change details. Review what your card actually contains; do not assume an omitted target is harmless. If the proposed action is wrong or unclear, reject it and ask for a corrected proposal. Review the corrected card rather than approving an earlier version. ## Approve or reject in chat 1. Read the pending card in **Assistant**, including the destination and any timing or recipient details. 2. Check the time remaining. **This approval has expired.** means it is no longer a live decision. 3. Select **Approve** only if the exact proposal is right. Select **Reject** to decline it. 4. Wait for the decision and action result. A disabled button during processing prevents repeated decisions. 5. Check the outcome in the relevant campaign or connected service. Approval alone is not proof that the external action succeeded. WhatsApp approval requests must be approved or rejected in WhatsApp. Their view in the web app is read-only. ## Allow publishing without asking The **Assistant approvals** settings card controls publishing. It is not a master switch for every sensitive tool, email, deletion or paid-ad action. 1. Open **Settings** → **Assistant** → **Assistant approvals**. 2. Find **Let the assistant publish without asking**. When off, every publish waits for your approval in chat. 3. To enable it, turn on the switch. The **Publish without asking?** confirmation appears. 4. Read the warning: the assistant can publish to your channels on its own, and a post can be seen before you remove it. 5. Choose **Turn it on** to confirm or **Cancel** to leave it off. 6. Wait for saving to finish. There is no separate save button. You can turn the switch off again directly to return to asking before publishing. > **Important:** Automatic publishing changes who reviews a real external action. Enable it only when you intend the assistant to publish without a fresh approval each time. It does not guarantee that every proposed publication is appropriate. ## Outside-content safeguards | Setting | What it does | | --- | --- | | **Ask again when the conversation has read outside content** | Reintroduces publishing review after outside material has been read. Pages and files may contain instructions written by someone else. This setting only has an effect when publishing without asking is enabled. | | **Treat files your team uploads as safe** | When on, an uploaded image or document alone does not send publishing back for review; web pages still can. Turn it off if a file may originate outside your team. | The outside-content switch is disabled when automatic publishing is off because every publish already waits for review. The file-trust switch, when available, is disabled unless both automatic publishing and the outside-content safeguard are on. If the file-trust row is not shown, that control is not available in this workspace's current service. Its absence is not an instruction to upload untrusted files or a guarantee that the file contents are safe. ## If something goes wrong - The approval expired: ask the assistant to prepare a fresh proposal and review it again. - The target or content is wrong: select **Reject**, explain the correction and wait for the revised proposal. - An approval decision or external action fails: inspect the result before repeating a send or publish. Avoid duplicate requests while the outcome is unclear. - A settings change shows **That change did not save. Try again.**: the card returns to the previous value. Recheck the switches and retry; do not rely on the value you clicked before the error. - The card fails to load: use **Retry**. Do not assume an approval policy from a failed load. - A safeguard switch is disabled: check the prerequisite switches above; this is different from a failed save. ## Related pages - [Assistant overview](https://docs.lead-knight.com/en/assistant/overview/). - [Chat and give a task](https://docs.lead-knight.com/en/assistant/chat/). - [Settings](https://docs.lead-knight.com/en/settings/overview/). - [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). ## Assistant settings: memory, writing style and approvals [Assistant settings: memory, writing style and approvals](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M4/nadlanite-en-348904e0695c.mp4) 1. In Settings, the Assistant section shows what the assistant has learned and remembers about you. 2. To shape how it writes for you, click Add preference. 3. Describe your style in a few words, and save. 4. It now writes in your style, for you only. 5. Approvals decide whether it publishes on its own. Off means every publish waits for you. 6. Once WhatsApp is connected, it can also send reminders and a morning briefing. --- # Assistant memory and writing style Review remembered rules and personal facts, dismiss learned conclusions and manage the writing preferences used in your workspace. Canonical: https://docs.lead-knight.com/en/assistant/memory-and-writing-style/ ## Three different kinds of context Open **Settings** → **Assistant**. The page has separate controls for explicit memories, learned information and writing preferences. | Card | What it contains | Who it affects | | --- | --- | --- | | **What the assistant remembers** | Explicit remembered **Rule** and **Fact** items. | Rules apply across the workspace. Facts belong to you alone. | | **What the assistant has learned** | Conclusions learned from conversations and observed outcomes, with scope and supporting evidence. | A workspace-wide item affects workspace members; a personal item affects its owner. | | **Writing style** | **Prefer** and **Avoid** preferences for AI writing. | Only your writing in the current workspace. | Business facts belong in **Business identity** in [Settings](https://docs.lead-knight.com/en/settings/overview/). Archiving a conversation is another separate action: it hides the chat but does not erase the assistant's memory. ## Before you start Check the workspace and the scope of the item. Removing a shared rule or dismissing a workspace-wide conclusion can affect other people. Personal writing preferences do not change everyone else's writing. Use clear, factual instructions. For example, a preference for short sentences belongs in writing style; an instruction that should apply to everyone in the workspace belongs to shared context. Do not store passwords or API keys as assistant memories. ## Ask the assistant to remember something 1. Open **Assistant** and state what should be remembered. 2. Be explicit about scope: is it your own fact, or a standing rule for this workspace? 3. Read the response rather than assuming every sentence in a conversation was stored as a memory. 4. Open **Settings** → **What the assistant remembers** to check the resulting item and its **Rule** or **Fact** label. If the card says **Nothing remembered yet. Ask the assistant to remember something.**, there are no items to display in that list. This is not a statement that the chat archive is empty. ## Remove remembered information 1. In **What the assistant remembers**, read the item and its scope. 2. Select **Forget** beside one item to remove it from the assistant. 3. To remove the workspace's shared rules and your own facts together, select **Forget everything**. 4. Read the confirmation carefully. Confirm with **Yes, forget everything**, or select **Cancel** to keep the memories. Bulk forgetting cannot be undone. It does not mean that another member's private facts are being shown or deleted. > **Important:** Forgetting removes a memory from the assistant immediately. Activity records that may include that memory's text can be kept for up to 180 days for security auditing, then deleted. Forgetting is not a promise of instant removal from every audit record. ## Review learned conclusions 1. Find **What the assistant has learned**. 2. Read the conclusion, scope, subject, supporting-source count and when it was last supported. Labels such as **User stated**, **Observed** or **Contested** help you interpret it; they do not make an incorrect conclusion true. 3. If the conclusion should no longer be used, select **Dismiss**. 4. Read the confirmation, especially for a workspace-wide item. Select **Dismiss belief** to confirm. Dismissing suppresses that exact value. The assistant can still learn a corrected value later. If the card says that only recent beliefs are shown, older ones are not available there to review or dismiss. If your role can view but cannot dismiss an item, the app explains the restriction. Ask someone with the appropriate workspace role rather than repeatedly submitting the dismissal. ## Add or edit writing preferences 1. Find **Writing style**. The counter shows the number of saved preferences out of 30. 2. Select **Add preference**. An editor appears. 3. Choose **Prefer** for something you want more of, or **Avoid** for something to leave out. 4. Enter a concise preference, up to 200 characters. For example, “short sentences” or “avoid sales jargon” describes a style, not a business fact. 5. Select **Save**. Check that the saved preference appears in the list. 6. Use **Edit** on an existing row to change its text or type, then **Save**. Use **Cancel** to leave the editor without saving. The card allows up to 30 preferences. Preferences can also be learned when you close **Discuss** in the AI writing interface. Review the resulting list if a writing habit is no longer useful. ## Delete writing preferences - **Delete** removes the selected preference. - **Clear all** opens a confirmation for all of your writing preferences in this workspace. Confirm with **Clear all**, or choose **Cancel**. Clearing writing preferences is separate from **Forget everything** and from dismissing learned conclusions. Use the control for the kind of context you actually want to change. ## If something goes wrong - You removed a chat but the assistant still uses a preference: archive and memory are different. Find the relevant memory, learned conclusion or writing preference and remove it there. - **Add preference** is disabled: wait for loading or a save to finish, or remove an unneeded preference if the count is 30. - A style preference cannot be saved: enter non-empty text within 200 characters and check the displayed error. - A load or delete operation fails: use **Retry** where offered and wait for confirmation. Do not treat a failed request as successful forgetting. - Dismissal is forbidden: ask an appropriately authorized workspace member. Changing the wording in the chat does not bypass the permission. ## Related pages - [Assistant overview](https://docs.lead-knight.com/en/assistant/overview/). - [Past chats](https://docs.lead-knight.com/en/assistant/past-chats/). - [Settings and business information](https://docs.lead-knight.com/en/settings/overview/). ## Assistant settings: memory, writing style and approvals [Assistant settings: memory, writing style and approvals](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M4/nadlanite-en-348904e0695c.mp4) 1. In Settings, the Assistant section shows what the assistant has learned and remembers about you. 2. To shape how it writes for you, click Add preference. 3. Describe your style in a few words, and save. 4. It now writes in your style, for you only. 5. Approvals decide whether it publishes on its own. Off means every publish waits for you. 6. Once WhatsApp is connected, it can also send reminders and a morning briefing. --- # Ask for a video guide in chat Describe what you want to learn and get a matching recorded guide with written steps in the assistant conversation. Canonical: https://docs.lead-knight.com/en/assistant/video-guides/ ## What this is for Ask the assistant for help with a product task, such as finding the setting for your workspace time zone. It can search the available guide catalog from your description and send a matching recording with written instructions. The assistant matches guide titles and summaries; it does not need to watch the recording to find a guide. A guide is instruction for you, not a claim that the assistant has carried out the task. ## Before you start Use the workspace and interface language you intend to work in. Describe the actual task rather than asking only for “a video.” Recordings are available for cataloged topics, not every possible screen or problem. You do not need to know a guide ID or an internal file name. Ordinary language is enough. ## Find and play a guide 1. Open **Assistant**. 2. Ask for the topic you need, for example: “Show me the video about changing the workspace time zone.” This is a sample request, not a required command. 3. If the assistant asks which task you mean, specify it. For example, distinguish workspace time zone from changing the interface language. 4. When a matching guide is sent, read its title and written steps in the conversation. 5. Select **Play guide** on the preview to open the video player. Use the player controls to play or pause while following the instructions. 6. Carry out the steps in the relevant app screen, then verify the setting or result there. The guide card contains its own written steps. You can follow them without playing the whole video. Starting playback does not press the buttons in your workspace for you. ## Language and edition notes The guide search uses your request in your own language. If the recording was made in the other edition, the card displays a note explaining that some screens may look different. Follow your current app's labels and permissions rather than assuming every detail of a recording is identical. LeadKnight and Nadlanite share many workflows, but this note is not a promise that every edition-specific feature exists in both. ## Guides in WhatsApp When chatting with the assistant in WhatsApp, a matching guide is delivered as a link with written steps. Where the richer delivery is unavailable, the assistant can provide the link and steps as text. Do not expect the embedded web guide card to appear inside WhatsApp in the same layout. Open the provided link to view the recording. It is help content, not a publishing approval or a connection code. ## If something goes wrong - No guide is found: describe a more specific task or ask for written help. Not every product action has a recording; a missing result must not be treated as a hidden video that always exists. - The wrong topic appears: state the difference and ask for a guide for the correct task. - The recording looks different from your screen: check the other-edition note, the interface language and whether the feature is enabled in the workspace. - Playback does not start automatically: use the video's play control. You can still read the written steps. - The task needs permission or a connected account: the video does not grant either. Complete the required setup in the app before repeating the relevant step. ## Related pages - [Assistant overview](https://docs.lead-knight.com/en/assistant/overview/). - [Chat and give a task](https://docs.lead-knight.com/en/assistant/chat/). - [Settings](https://docs.lead-knight.com/en/settings/overview/). - [Troubleshooting and FAQ](https://docs.lead-knight.com/en/troubleshooting/overview/). --- # Campaigns and Properties Find campaigns and properties, understand their posts and network cards, and choose the right guide for creation, scheduling, management and results. Canonical: https://docs.lead-knight.com/en/campaigns/overview/ ## Find your campaigns In LeadKnight, **Campaigns** brings together each goal, its content and its publications. In the Nadlanite real-estate edition the same `/campaigns` page is called **Properties**, and the entry action is **New property** rather than **New campaign**. The workspace edition determines the wording; these are not two menus you must keep in sync. 1. Open **Campaigns** or **Properties**. 1. Use **Search by name or goal** to find an item. 1. Choose **Sort**: **Recently updated**, **Newest first**, **Name** or **Most urgent**. 1. Use **Status**, **From date** and **To date** to narrow the list. **Clear dates** removes the date bounds. 1. Under **View**, choose **Cards** or **List**. Open an item's card or row to reach its board. 1. Expand the archived section to find archived items. An empty current section does not mean the archive is empty. Cards show **Posts today**, **Last 7 days**, **Active posts** and **Active networks** where available. An included paid-ad or linked-site indicator is a pointer to that association, not proof that an ad is delivering or that every post succeeded. If there are no items, the page invites you to use the new-item action. On phones with existing items, the page's new-campaign button may be hidden; use the navigation add control. ## Understand the structure - A campaign holds related content for a goal; in Nadlanite, a property holds related property marketing. - A post holds text and media. - A network card represents that post on a particular account/network and format. Its destinations, schedule and state can differ from another card of the same post. - An ad set groups cards inside the board. A folder alone is not a launched paid advertisement. Open the [campaign board guide](https://docs.lead-knight.com/en/campaigns/campaign-board/) for filters, post popups, ad-set folders, publication outcomes and attention messages. ## Create and add content | I want to… | Guide | |---|---| | Write and publish the first post myself | [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) | | Give AI a brief, choose content types/ideas and review a sample | [Create a campaign with AI](https://docs.lead-knight.com/en/campaigns/create-with-ai/) | | Add content without creating another campaign | [Add another post](https://docs.lead-knight.com/en/campaigns/add-post/) | | Create, improve or discuss wording inside the composer | [AI writing tools](https://docs.lead-knight.com/en/campaigns/ai-writing/) | | Set one-time, recurring or Facebook-group timing | [Scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) | | Edit, pause, resume, archive, restore or remove future sends | [Manage campaigns](https://docs.lead-knight.com/en/campaigns/manage-campaign/) | Manual publishing is an explicit approval to send to the chosen destinations and schedules. AI creation has a review pause: inspect the generated content and use **Resume all** when ready. Saving, scheduling and background creation are not themselves proof of publication. ## Nadlanite property path The property AI flow uses structured property details and skips the general content-types/ideas steps: 1. [Enter address, contact and property details](https://docs.lead-knight.com/en/campaigns/property-details/). 1. [Describe the property, upload media and choose the photo policy](https://docs.lead-knight.com/en/campaigns/property-media/). 1. [Choose destinations, review the sample and create](https://docs.lead-knight.com/en/campaigns/property-publish/). 1. Review the paused posts on the board, then **Resume all**. ## Results and next steps Use the board's **Summary** and individual network-card metrics to inspect performance. A scheduled or active campaign is not a delivery receipt for every destination. For broader reporting see [analytics](https://docs.lead-knight.com/en/analytics/overview/), and for date-based content management see [calendar](https://docs.lead-knight.com/en/calendar/overview/). ## If something goes wrong - **Nothing matches these filters.**: clear the search, status or date restrictions before assuming content disappeared. - **Creating the campaign**: background work is still running. Open the board to see posts as they become ready. - **Waiting to continue** with an allowance message: follow the displayed continuation time. The page explains when creation resumes automatically. - **Creating the campaign didn't finish**: inspect the board for already-created posts rather than assuming none exist. - **Needs attention**: open the card's explanation and follow the cause-specific fix. - Facebook-group publishing waits on the browser: see [extension installation and pairing](https://docs.lead-knight.com/en/extension/install-and-pair/). For wider help, use [troubleshooting](https://docs.lead-knight.com/en/troubleshooting/overview/). ## Your Campaigns page [Your Campaigns page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G1-GEN/leadknight-en-98773676f7ca.mp4) 1. Campaigns is where every campaign lives, with its content and posts. 2. Start one with New campaign. 3. Search for a campaign by name. 4. Filter by status, or by date range. 5. Switch between cards and a compact list. 6. No campaigns yet? Press New campaign to create your first one. ## Your Properties page [Your Properties page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G1-RE/nadlanite-en-d884677cfda7.mp4) 1. Properties is where every property campaign lives, with its content and posts. 2. Add a property with New property. 3. Search for a property by name. 4. Filter by status, or by date range. 5. Switch between cards and a compact list. 6. No properties yet? Press New property to add your first one. ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Create a campaign manually Choose a goal, write a post, add media and destinations, review the preview and approve publishing on the chosen schedule. Canonical: https://docs.lead-knight.com/en/campaigns/create-manual/ ## What this is for Choose the manual path when you want to write the post yourself and choose its media, destinations and timing. You can still use the [AI writing tools](https://docs.lead-knight.com/en/campaigns/ai-writing/) without asking AI to build an entire campaign. ## Before you start - Connect the accounts you want to use: [social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) and [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/). - For browser-extension Facebook-group posting, [install and pair the extension](https://docs.lead-knight.com/en/extension/install-and-pair/), sign into the intended Facebook account and keep Chrome open. - Prepare the text and any photos/videos you own or may use. Check which account or Page should publish. ## Choose the campaign's purpose 1. Open **Campaigns** and choose **New campaign**. On phones, if that page button is not shown, use the navigation's add control. 1. At **What is the campaign's goal?**, choose **Leads**, **Promote an event**, **Sales**, **Traffic** or **Other**. 1. For an event, answer **Which event?**; for sales, **What are you selling?**. Choose a recent answer or write a new one and continue. For **Other**, fill in **What is the goal?** and press **Continue**. 1. At **How urgent is this campaign?**, choose one to five stars and continue. Urgency controls relative priority and the pace of content creation; it is not a guaranteed publishing count. 1. If **Who gets this campaign's leads?** appears, choose the intended person or **As usual — whoever runs the ad or the website**, then continue. This question depends on the workspace's team. 1. At **Who creates the campaign content?**, choose **Me**. > **Note:** In Nadlanite the entry is **Properties** → **New property**. New properties skip the general goal/detail questions and use property urgency and lead-owner wording. Choosing **Me** opens the manual composer; the structured AI property flow is explained in [property details](https://docs.lead-knight.com/en/campaigns/property-details/). ## Write the post and add media 1. In **Post content**, write the message. **Name** is optional; use it to recognize the post. 1. Choose **Upload photos or videos** or **Add media** to attach files. Wait for **Uploading…** to finish. Adding media advances to network selection. 1. For a text-only post, choose **Continue without adding media**. Networks/formats that require a photo or video still need suitable media. 1. Review the attached files. Use **Remove media** to remove the wrong item. You can also **Create an image from the text** after writing the post. The manual text limit is 10,000 characters, and individual networks can impose smaller limits. The UI shows the applicable media-file limit and network-specific restrictions; do not treat one network's accepted format as universal. ## Choose destinations and review 1. Under **Networks**, click the network you want. Select the intended **Accounts** and **Where to publish**, such as **Feed post**, **Story** or **Reel**, where offered. 1. For **Facebook groups**, select the publishing identity and choose folders or individual groups. Finish the selection with **Done**. Complete any shared-folder confirmation shown; a folder is a live selection, not necessarily a frozen list. 1. Add the other networks you need. Check their account names, formats and destination summaries before continuing. A selected platform name alone is not enough if its account or groups are missing. 1. Press **I'm done**. The **Preview** appears. 1. Read the text, check media and inspect the network previews. Use **Add or edit networks** to correct the destinations. 1. Press **Finish**. **When should the post go out?** appears. ## Schedule and approve publication 1. Review each network/account. Keep a one-time feed post, choose an explicit repeat where supported, or set the Facebook-group publishing window. See [scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/). 1. Review **Post priority**, and any required confirmations for messages to people. 1. Press **Publish to the campaign**, or **Publish to the property** in Nadlanite. This is the current manual publishing control: the publish/start action is your grant to send this content to the selected destinations on its schedules. It is not just a preview or draft save. 1. To save without granting publication, choose **Save as a draft in the campaign** or the corresponding property action instead. 1. Read the completion result, then view the campaign. Check its network cards and actual publication results. > **Important:** A successful save or queued/scheduled card is not proof of a live post. AI-created campaigns use a different review gate: they start paused and require **Resume all** after review. ## If something goes wrong - **Write the post's text**: enter the message before continuing. - **Choose at least one network** or **Choose at least one folder or group**: complete the destination selection, not just the platform choice. - **Wait for the media to finish uploading**: wait before submitting; remove and upload unavailable media again. - **Needs a photo or video** / **Needs a video**: attach media suitable for that format or choose another format. - **Reconnect this account before publishing.**: repair the [social connection](https://docs.lead-knight.com/en/channels/connect-social-accounts/). - The extension is offline: [restore its connection](https://docs.lead-knight.com/en/extension/install-and-pair/). Do not publish a second copy to bypass the wait. - A completion result reports a network was not published: fix the reason, then use **Try again** on its card. Other successful networks do not make this one successful. ## Related pages - [Campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Add another post](https://docs.lead-knight.com/en/campaigns/add-post/) - [Create with AI](https://docs.lead-knight.com/en/campaigns/create-with-ai/) ## Choose your campaign goal and urgency [Choose your campaign goal and urgency](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F1/leadknight-en-f06ec11c91f2.mp4) 1. To create a campaign, click New campaign. 2. First, choose what the campaign should achieve. Here, we choose Sales. 3. Then write what you are selling, and continue. 4. Set how urgent the campaign is. Urgency decides its priority and how fast content is created. 5. Finally, choose who creates the content: you, or the AI. 6. We let the AI create it. Next, you tell the AI about the campaign. ## Choose where your campaign is posted [Choose where your campaign is posted](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F3/leadknight-en-c17b256a35b8.mp4) 1. After you describe the campaign, click Continue and choose where to publish. 2. Click the Facebook page to post on it. 3. For Facebook groups, choose which groups to post in. 4. You can pick a whole folder, or search for single groups. 5. Tick the group, then click Save. 6. Click Continue to choose what the AI creates. --- # Create a campaign with AI Give the AI a brief, choose photos, networks, content types and ideas, review a sample, then create paused content for your approval. Canonical: https://docs.lead-knight.com/en/campaigns/create-with-ai/ ## What this is for AI creation prepares campaign content and publishing schedules from your goal, business context and choices. You review a sample before creating, then review the resulting posts before starting them. > **Important:** The campaign is created paused. Nothing is published until you review it and press **Resume all**. A sample is not the finished set of campaign posts. ## Before you start Connect the [social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) and [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) you plan to use. Check your profile and business information: the brief screen shows which context the AI will use. Prepare accurate facts and media you may publish. In Nadlanite, choosing AI opens a shorter property-specific sequence: property details → brief/photos → networks → sample. Use [the property guide](https://docs.lead-knight.com/en/campaigns/property-details/); the general content-types and ideas screens below are not extra required property steps. ## Choose the goal and AI creator 1. Open **Campaigns** → **New campaign**. 1. Choose **Leads**, **Promote an event**, **Sales**, **Traffic** or **Other**. Complete the event, sales or other-goal detail if requested. 1. Choose one to five urgency stars. Continue and choose who receives leads if the team-dependent question appears. 1. At **Who creates the campaign content?**, choose **The AI**. The AI creation steps open. ## Brief and photos 1. In **About the campaign (optional)**, describe the offer, price, audience, tone and any facts the AI must respect. The field can be skipped; then the AI works from the goal and business profile. Keep the brief within 8,000 characters. 1. Under **Media (optional)**, use **upload media** or drag in photos/videos. Wait for uploading to finish. You can continue without media; the AI can create images. 1. If photos are attached, choose how they may be used: - **Use my photos as they are** keeps the supplied photos. - **Enhance my photos — and create more like them** allows enhancement and additional inspired images. - **Create new images inspired by my photos** allows newly generated imagery. 1. Review **The AI will also use:**. Where available, choose **Other campaigns (choose)** to supply earlier campaign context; use **Done** to confirm that selection. 1. Press **Continue**. ## Networks, content types and ideas 1. At **Where to publish?**, choose the networks, accounts and targets. For **Facebook groups**, choose folders or individual groups and the intended publishing identity. 1. Open **Edit the choice** to review each target. Complete any confirmation that folders are resolved when each post goes out. If a network is missing, connect it in Connections rather than assuming AI can post there. 1. Press **Continue**. Under **What would you like to create?**, select the content types you want: **Reels**, **Stories**, **Image or carousel**, **Flyers** or **Text post**. 1. Continue to **Pick the ideas for the campaign** and wait for suggestions. 1. Tick the ideas you want. Each idea becomes an ad set, organizing related content; that alone does not launch a paid ad. 1. To change an idea, use **Edit**, update **Idea title** and **Idea angle**, then **Done**. Use **More ideas** for additional suggestions. 1. If paid-ad options are available and you select them, review their separate settings and idea selections. A prepared paid draft is not permission to spend; see [paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). ## Review the sample and create 1. Continue to **Here's how a post from this campaign will look**. Wait for the sample. 1. Read **Full text** and check the image. Verify facts, tone and every text variation shown. 1. Under **What should change?**, describe a correction and press **Update the sample**. Repeat until the sample reflects your instructions. Review **Changes you asked for** and remove an instruction if it is no longer wanted. 1. Use **Another image** if you want another sample image and the option is available. 1. Read the paused-creation notice, then press **Create the campaign**. Creation continues in the background. 1. Return to the campaign board. Posts appear as they become ready. Inspect every post and any generated videos, then choose **Resume all** when ready to start the paused content. ## If something goes wrong - **Pick at least one network**, **Pick at least one content type** or **Pick at least one idea**: return to that step and make a selection. - **Every idea needs a title and an angle**: complete both fields in the edited idea. - **A sample is needed first**: wait for or retry sample creation before creating the campaign. - **We couldn't create a sample. You can try again.**: retry without discarding the brief. - **Today's AI writing allowance is used up — you can continue tomorrow**: continue after the stated allowance resets; repeated clicks do not add capacity. - **We couldn't make a sample image — the campaign will still create images**: this is a sample-image failure, not proof the entire campaign failed. - **We could not create the campaign. You can try again.**: retain your choices and retry. On the board, distinguish unfinished background creation from posts that already exist. ## Related pages - [Campaign board and review](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) - [Add AI posts to an existing campaign](https://docs.lead-knight.com/en/campaigns/add-post/) ## Choose your campaign goal and urgency [Choose your campaign goal and urgency](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F1/leadknight-en-f06ec11c91f2.mp4) 1. To create a campaign, click New campaign. 2. First, choose what the campaign should achieve. Here, we choose Sales. 3. Then write what you are selling, and continue. 4. Set how urgent the campaign is. Urgency decides its priority and how fast content is created. 5. Finally, choose who creates the content: you, or the AI. 6. We let the AI create it. Next, you tell the AI about the campaign. ## Tell the AI about your campaign and add photos [Tell the AI about your campaign and add photos](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F2/leadknight-en-fa483e6abad7.mp4) 1. Tell the AI about the campaign in your own words. This step is optional. 2. Write what matters: the offer, the audience and the tone. 3. The AI also uses your profile and your business details. 4. Add your own photos or videos. Without media, the AI creates images itself. 5. Then choose how the AI uses your photos. Here, we keep them as they are. 6. Click Continue to choose where the campaign is posted. ## Choose where your campaign is posted [Choose where your campaign is posted](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F3/leadknight-en-c17b256a35b8.mp4) 1. After you describe the campaign, click Continue and choose where to publish. 2. Click the Facebook page to post on it. 3. For Facebook groups, choose which groups to post in. 4. You can pick a whole folder, or search for single groups. 5. Tick the group, then click Save. 6. Click Continue to choose what the AI creates. ## Choose content types and AI ideas [Choose content types and AI ideas](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F4/leadknight-en-411fe7121353.mp4) 1. Choose what the AI creates. You can pick several types. 2. Here we pick Image or carousel, because we added a photo. 3. Click Continue, and the AI suggests ideas for the campaign. 4. Every idea becomes a set of posts. Untick an idea that doesn't fit. 5. Click Edit to change its title or angle. 6. Want more? Click More ideas. 7. Then click Continue to see a sample. ## Review the AI sample and create the campaign [Review the AI sample and create the campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F5/leadknight-en-060a48a10308.mp4) 1. Here's how a post from the campaign will look, written the way the AI will write it. 2. You can see it on a phone or a desktop. 3. Want a change? Write a request and click Update the sample. 4. The campaign is created paused. No post goes out until you start it. 5. When the sample looks right, click Create the campaign. ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Use the campaign board and understand publication status Find posts, open their network cards, inspect attention messages and read campaign results without confusing a scheduled post with a confirmed publication. Canonical: https://docs.lead-knight.com/en/campaigns/campaign-board/ ## What the board contains Open a campaign from **Campaigns**, or a property from **Properties** in Nadlanite. The board at `/campaigns/:id` brings together the content and its network cards. A post can have several cards: each represents that post on one network/account and format, with its own settings and schedule. A campaign's overall status is a summary, not confirmation that every destination received every post. ## Find and open a post 1. Open the campaign card or row. 1. Under **Current posts**, use **Search posts**, the **Network** and **Ad set** filters, or **Filter by status**. 1. Switch **View** between **Cards** and **List** if another layout is easier. 1. Click a post card to open **Edit post**. Review its text, media, **Networks** and publishing times. 1. Close the popup to return to the board. Look in **Completed posts** for finished cards rather than assuming they were deleted. 1. To add content, choose **Add a post**. See [adding another post](https://docs.lead-knight.com/en/campaigns/add-post/). ## Status is not the same as a publishing result | Label | Meaning | |---|---| | **Draft** | The post is not approved to run in its current form. Review and publish it. | | **Scheduled** | The card is waiting for its scheduled publication; this does not prove delivery. | | **Active** | The card's run is active. Inspect its results and attention messages for the actual outcome. | | **Paused** | Sending is paused. AI-created posts start this way for review. | | **Finished** | The card's schedule/run has ended. A completed post can offer **Restart** to choose when it goes out again. | | **Archived** | The campaign was moved to the archive. Published posts remain online. | | **Needs attention** | A separate warning requiring inspection; it can accompany an otherwise scheduled or active card. | ### Failed, held and awaiting verification A failed attempt means the latest attempt did not complete successfully. Open the attention explanation: it shows **What happened**, **How to fix** and, when available, **The network's message:**. Fix the stated cause before choosing **Try again**. A held job is waiting rather than a confirmed publication. Reasons include a disconnected extension, a paused identity, possible duplicate content or a content update. **Updating the content · sends are paused** means the rewrite has not finished. Do not duplicate a post to get around a hold. An outcome awaiting verification is uncertain, not safely “failed.” Check the destination on the network before retrying. The posting guidance explicitly warns that a post may have gone out even when the extension reported an internal error. **Awaiting group admin approval** means the group administrator has not approved it yet; another publication is not the fix. ## Ad-set folders Use **Select cards**, tick the cards and choose **Group into an ad set**. Enter **Ad set name** to organize related cards. Open the set to see its posts; **Pause set**, **Resume set** and **Ungroup set** act on that grouping. An ad-set folder is not proof that a paid ad is live. Paid ads have separate controls and states. If paid-ad controls are not available in your workspace, do not assume the folder launches paid advertising. See [paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). ## Results and analytics In **Summary**, inspect **Performance**, **Total sends**, **Publications by network** and **What works best**. Cards show supported network metrics such as views, reach and comments, and posting counts such as **Posts today**, **Last 7 days**, **Last posted** and **Next post**. **Stats aren't available for this channel** and **—** are not zero-result measurements. For broader reporting, see [analytics](https://docs.lead-knight.com/en/analytics/overview/). ## If something goes wrong - **The page couldn't load.**: retry loading. A not-found message is different; use **Back to Campaigns** or **Back to Properties** to locate the correct item. - **Extension disconnected**: open Chrome with the extension and keep it open. See [installation and pairing](https://docs.lead-knight.com/en/extension/install-and-pair/). - **Facebook sign-in unavailable**: sign into the correct Facebook account in the browser with the extension. - **Possible duplicate** or an uncertain outcome: check the group for an existing post before retrying. - **The post changed after it was approved — save it again to publish.**: open the post, review the current content and approve that version. - **Building this campaign didn't finish. The posts that were ready are below.**: review the posts that exist; do not assume every planned post was created. ## Related pages - [Scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) - [Pause, archive and edit](https://docs.lead-knight.com/en/campaigns/manage-campaign/) - [Campaign results and analytics](https://docs.lead-knight.com/en/analytics/overview/) ## Your Campaigns page [Your Campaigns page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G1-GEN/leadknight-en-98773676f7ca.mp4) 1. Campaigns is where every campaign lives, with its content and posts. 2. Start one with New campaign. 3. Search for a campaign by name. 4. Filter by status, or by date range. 5. Switch between cards and a compact list. 6. No campaigns yet? Press New campaign to create your first one. ## Your Properties page [Your Properties page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G1-RE/nadlanite-en-d884677cfda7.mp4) 1. Properties is where every property campaign lives, with its content and posts. 2. Add a property with New property. 3. Search for a property by name. 4. Filter by status, or by date range. 5. Switch between cards and a compact list. 6. No properties yet? Press New property to add your first one. ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Schedule posts and repeat publishing Understand one-time posts, optional weekly or monthly repeats, and the publishing window for Facebook groups. Canonical: https://docs.lead-knight.com/en/campaigns/scheduling/ ## How scheduling works Each network/account card has its own schedule. By default, feed posts publish **Once** and Facebook groups continue within a publishing window. The current composer also offers explicit **Repeats** for eligible non-group networks; choosing a network does not turn recurrence on automatically. Marketplace listings publish once, with a separate **Renew listing** setting. Do not confuse renewal with publishing the same feed post repeatedly. ## Before you start Write the post, choose its networks and review the preview. Continue with **Finish** to **When should the post go out?**. Check the workspace time zone shown by the scheduling controls. ## Set a one-time post 1. Select the network/account whose time you want to change. 1. Press **Change** and keep **Once**. 1. Choose **Now**, or set a date and time. 1. Check the summary for that network. Repeat for other selected networks if they need different times. 1. Use **Apply to all networks** only when you want the same schedule on the other compatible networks. Facebook-group windows and Marketplace one-time schedules do not accept incompatible rules. ## Set an explicit repeat 1. For an eligible non-group network, choose **Repeats**. 1. Choose **Every week** or **Every month**. 1. Weekly: select at least one day under **Which days?**. 1. Monthly: enter **Which day of the month?**, from 1 to 31. 1. Enter **Time**, then choose **Until I stop it** or **Until a date** and an **End date**. 1. Review the summary. **The same text is published on every repeat.** For WhatsApp, the message goes to the same recipients each time. ## Set the Facebook-group window 1. Select **Facebook groups** in the timing screen. 1. Choose **Now, no end date** or **Start and end dates**. 1. For a date range, choose **Start date** and optionally **End date (optional)**. The end must follow the start. 1. Review **Post priority**. The stars set the post's share of the Facebook-groups budget and its precedence when posts compete for the same time; they are not a promise of a fixed number of publications. 1. Publish the manual post, or review an AI-created campaign and choose **Resume all**. Setting a time alone is not proof that a post was sent. ## Pauses and missed times When resuming shows **You missed posts**, choose **Send one now** or **Continue from the next time**. This is a choice about missed publications, not an instruction to resend every missed occurrence. ## If something goes wrong - **Choose at least one day**: select a weekday before saving a weekly rule. - **Choose a valid time (HH:MM)**: correct the time field. - **The end date must be after the start date**: move the end later or clear the optional group end. - **The publishing time has passed. Choose a new time.**: set a future time and review again. - **Fix the publishing time marked in red**: inspect each network, not just the selected one. - A group card waits for the extension: [install and pair the extension](https://docs.lead-knight.com/en/extension/install-and-pair/). Do not create a second copy just to bypass a wait. ## Related pages - [Manual campaign](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Campaign board and publication status](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Calendar](https://docs.lead-knight.com/en/calendar/overview/) ## Choose where your campaign is posted [Choose where your campaign is posted](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/F3/leadknight-en-c17b256a35b8.mp4) 1. After you describe the campaign, click Continue and choose where to publish. 2. Click the Facebook page to post on it. 3. For Facebook groups, choose which groups to post in. 4. You can pick a whole folder, or search for single groups. 5. Tick the group, then click Save. 6. Click Continue to choose what the AI creates. ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Add another post to an existing campaign Add a manual post or an AI batch without creating a separate campaign or repeating its goal and urgency questions. Canonical: https://docs.lead-knight.com/en/campaigns/add-post/ ## What this is for Use **Add a post** when new content belongs to a campaign or property you already manage. The route `/campaigns/:id/add` keeps it in that campaign rather than making a new one. ## Before you start Open the intended campaign and check its name. An archived campaign cannot accept more posts, and a campaign still being created may ask you to wait. Connect any extra networks before you need them. ## Add a manual post 1. In the [campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/), choose **Add a post** on the add tile or row. 1. At **Who creates the post?**, choose **Me**. Goal and urgency are not asked again: they already belong to the campaign. 1. Write **Post content**, and optionally **Name**. 1. Add photos or videos with **Upload photos or videos**, use the campaign's media bank, or choose **Continue without adding media**. 1. Choose **Networks** and configure the accounts, formats and groups for this post. Do not assume another post's destinations are automatically the right ones. 1. Press **I'm done**, inspect **Preview**, then **Finish** to set the publishing time. 1. Review every network's schedule. Choose **Publish to the campaign** or, in Nadlanite, **Publish to the property** to approve publication on those schedules. To keep it unapproved, use the draft action instead. 1. On the confirmation screen, choose the view action to return to the campaign, or **Create another post** to continue adding. See the [manual flow](https://docs.lead-knight.com/en/campaigns/create-manual/) for network and media choices in detail. ## Add posts with AI 1. Choose **The AI** at the creator question. 1. In **Add posts with AI**, enter the brief and optional media, then review networks and the subsequent choices offered. 1. Review the sample and request changes before creating. Existing campaign context is reused; you are not setting a new campaign goal. 1. Return to the board and review the created content. AI-added posts are created paused, including additions to an already active campaign. Use **Resume all** only after checking the paused content. A calendar-selected time or an explicit manual entry can open the manual composer directly without the creator question. This does not mean a goal or urgency answer was lost. ## If something goes wrong - **The campaign is still being created in the background. Try again in a moment.**: return to the board and allow creation to progress. - **The campaign is archived, so it takes no more posts.**: [restore it](https://docs.lead-knight.com/en/campaigns/manage-campaign/) if you intend to use it again; review its paused posts separately. - **Choose at least one network**: select a network and finish its account/recipient settings. - **Media in this post is no longer available. Upload it again.**: remove the unavailable item and upload it again. - A success screen reports **Not published on …**: read the reason. Correct it and use **Try again** on the campaign page; that network will not necessarily publish on its own. ## Related pages - [Create with AI](https://docs.lead-knight.com/en/campaigns/create-with-ai/) - [Scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) - [AI writing tools](https://docs.lead-knight.com/en/campaigns/ai-writing/) ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Edit, pause or archive a campaign Change campaign and post details, pause or resume sending, and understand what archiving and deleting do not remove from social networks. Canonical: https://docs.lead-knight.com/en/campaigns/manage-campaign/ ## Before you start Open the correct campaign or property and check its name. Campaign controls, individual post controls and paid-ad controls have different effects. Only use actions available to your account. > **Important:** The current general campaign menu offers archiving, not a permanent delete-campaign or a separate Stop button. Archiving is not deletion of published social posts. ## Edit campaign details 1. Open the [campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/). 1. Open **Summary** or expand it with **Expand the summary**. 1. Use **Edit name**, enter **Name** and press **Save**. A name is required. 1. Adjust **Urgency** if you need to change relative priority. Review **Goal** and **Leads go to** rather than assuming the author receives every lead. 1. In Nadlanite, use **Edit property details** for structured property fields. See [property details](https://docs.lead-knight.com/en/campaigns/property-details/). ### Change a fact used by several posts In **Key facts**, choose the relevant edit control, enter the value and **Save**. The board explains **Updating the posts… their sends are paused until it's done.** Check the result: a failed update can leave affected posts paused. **Undo** can reverse the fact change when offered. Property-linked fields direct you to the property details instead. ## Edit or delete a post 1. Click its card to open **Edit post**. 1. Change text or media. Use **Networks and schedule** to review destinations and timing, or **Add a network** where shown. 1. Press **Save**. If asked **Also update …?**, choose **Yes, on all networks** or the option for this network only. 1. Review any new approval/attention state. The post's previous approval does not authorize arbitrary later changes. 1. To stop future sends for the post, choose **Delete**. In **Delete post**, choose the single-network option or **Delete from all networks**, or **Cancel**. **Changes apply to future sends only. Posts that were already published stay as they are.** Deleting a post here also stops future sends only; it does not remove its already-published copies from social networks. ## Publish saved drafts from the board If **Publish campaign** with a post count is offered in **Summary**, open it and read **Publish this campaign?**. The confirmation states how many posts will start on their schedules. Check the warnings about posts without a network and posts that message people. Choose **Publish** only after reviewing the eligible drafts. WhatsApp/email posts are published from the post itself, and posts without networks cannot be published. Check marked cards if some were held back. This bulk draft approval is different from **Resume all**, which resumes paused cards. ## Pause and resume 1. From the campaign menu or **Summary**, choose **Pause all** to pause its post cards. 1. For a smaller scope, use **Pause** on one card or **Pause set** inside a set. 1. To continue, use **Resume all**, **Resume** or **Resume set** at the matching scope. 1. If **You missed posts** appears, choose **Send one now** or **Continue from the next time**. 1. For newly AI-created content, first review all posts and videos, then **Resume all**. This is the action that starts the reviewed paused content. ## Archive, restore and Marketplace deletion 1. Choose **Move to archive** in the campaign menu or summary. 1. Read the confirmation and confirm **Move to archive**. Unsent posts stop; published posts stay online. 1. Pause paid ads separately if you intend to stop spending. The archive confirmation explicitly says paid ads keep running and spending. 1. To return an archived campaign, find it under the archived section and choose **Restore from archive**, then **Restore**. Its posts return paused; review them before **Resume all**. If **Delete Marketplace listing** is offered, that is a separate action affecting Facebook. Its confirmation **Delete listing** removes the listing from Facebook and cannot be undone. Do not confuse it with archiving the campaign. ## If something goes wrong - **Enter a name.**: supply a non-empty name and save again. - **This post changed after you opened it. Your edits are still here — nothing was lost.**: decide what to keep before **Load the latest version**; loading replaces your edits. - **Updating this post failed, so it stays paused.**: use **Try the update again**, or carefully review **Keep the old text**. Keeping the old text resumes sending without the requested change. - **This ad set has paid ads. Delete or end them first.**: resolve its paid ads before attempting the blocked set action. - **That didn't work. Try again.**: inspect the current state before retrying; do not assume a failed action changed it. ## Related pages - [Publication status and attention](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Scheduling and missed times](https://docs.lead-knight.com/en/campaigns/scheduling/) - [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) ## Your Campaigns page [Your Campaigns page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G1-GEN/leadknight-en-98773676f7ca.mp4) 1. Campaigns is where every campaign lives, with its content and posts. 2. Start one with New campaign. 3. Search for a campaign by name. 4. Filter by status, or by date range. 5. Switch between cards and a compact list. 6. No campaigns yet? Press New campaign to create your first one. ## Your Properties page [Your Properties page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G1-RE/nadlanite-en-d884677cfda7.mp4) 1. Properties is where every property campaign lives, with its content and posts. 2. Add a property with New property. 3. Search for a property by name. 4. Filter by status, or by date range. 5. Switch between cards and a compact list. 6. No properties yet? Press New property to add your first one. ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Write and improve a post with AI Use Create new, Improve or Discuss inside the post composer, then review the text before publishing. Canonical: https://docs.lead-knight.com/en/campaigns/ai-writing/ ## What this is for The composer's **AI** menu helps write one post. It is different from creating a whole [campaign with AI](https://docs.lead-knight.com/en/campaigns/create-with-ai/): you keep control of this post's networks and publishing time. ## Before you start Open the manual composer for a new campaign or [add a post](https://docs.lead-knight.com/en/campaigns/add-post/) to an existing one. To improve existing text, write or paste it into **Post content** first. ## Create new text 1. Open **AI** and choose **Create new**. 1. Under **What should the new post be about?**, describe the message, audience and facts to include. 1. Choose **Length**: **Short**, **Medium** or **Long**. 1. Choose whether to use **With variations**. Review the resulting alternatives rather than assuming every version says the same thing. 1. Press **Create post**. Check the proposed wording, especially names, prices and contact details. ## Improve or discuss a draft 1. For a direct rewrite, open **AI** and choose **Improve**. 1. For a conversation, choose **Discuss**. The panel shows **Your draft**. 1. Write a request in **What would you like to change or explore?**, then press **Send**. 1. Read the updated draft. Suggestions can update the composer; use **Undo** if the result is not right, or **Redo** to restore a change. 1. If you edited the draft while a suggestion was being prepared, the message **You edited the draft. Your text is safe.** protects your newer text. Review the suggestion and use **Apply suggestion** only if you want it. 1. Close the conversation and continue through media, networks, preview and scheduling. AI writing does not itself publish the post. ## Writing preferences and recovery **Writing style** contains preferences learned when you close **Discuss**, or ones you add there. They apply only to your writing in the current workspace. Use **Prefer**, **Avoid**, **Add preference**, **Save** and **Delete** to keep them accurate. **Clear all** asks for confirmation. If **Restore your unsaved draft?** appears, choose **Restore** to recover it or **Discard** to remove it. Review recovered text and media before publishing. ## If something goes wrong | What you see | What it means | What to do | |---|---|---| | **AI writing is unavailable. Your text was not changed.** | The writing action is unavailable. | Keep editing manually; do not assume a rewrite was applied. | | **Couldn’t complete that. Your draft is safe; try again.** | The request failed without replacing your draft. | Keep the draft and retry the request. | | **The AI couldn’t create valid variations. Try again or turn off With variations.** | The alternatives could not be prepared correctly. | Retry or turn **With variations** off. | | **You’ve used today’s assistant allowance.** | The daily allowance was reached. | Follow the reset time shown, or write manually. | ## Related pages - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Create a campaign with AI](https://docs.lead-knight.com/en/campaigns/create-with-ai/) - [Edit and manage campaigns](https://docs.lead-knight.com/en/campaigns/manage-campaign/) --- # Enter and update property details Start a Nadlanite property, enter its address and contact information, and understand the optional numeric fields before creating AI content. Canonical: https://docs.lead-knight.com/en/campaigns/property-details/ ## What this is for Nadlanite uses **Properties** and **New property** where the general LeadKnight edition uses campaigns. Both use the campaign board, but the property AI path asks for structured listing details rather than the general campaign goal and ideas. This page covers the property-details part of the flow. Continue with [description and photos](https://docs.lead-knight.com/en/campaigns/property-media/), then [destinations, sample and creation](https://docs.lead-knight.com/en/campaigns/property-publish/). ## Before you start Prepare the property's address and a contact phone. Have the price, city, measurements and contact details available if you want them included. Contact information is prefilled from your profile; check it rather than assuming it is correct for this listing. ## Start the property 1. Open **Properties** at `/campaigns` and choose **New property**. 1. At **How urgent is this property?**, choose one to five stars and continue. The property path skips the general campaign goal/detail questions. 1. If **Who gets this property's leads?** appears, choose the intended recipient or the usual-recipient option. 1. At **Who creates the property content?**, choose **The AI**. Choosing **Me** opens the [manual composer](https://docs.lead-knight.com/en/campaigns/create-manual/) instead. 1. The **Property details** step shows **About the property** and **Contact details**. ## Fill in the details 1. Enter **Address**. This is required. 1. Add **City** if available. For Buy-and-Sell group publishing, the board specifically asks for a city and price; an address alone is not a substitute. 1. Fill optional **Rooms**, **Bathrooms** and **Area (sqm)** with known facts. Leave unknown optional values blank instead of inventing numbers. 1. Enter **Asking price** and check **Currency** if supplying a price. 1. Review **Contact name** and **Contact phone**, including prefilled values. A contact phone is required. 1. Press **Continue**. The next step is the property's description and optional media; completing this form alone does not create or publish a property. ### Numeric rules | Field | Accepted values | |---|---| | **Rooms** | 0 to 50, in half-room increments, such as 3 or 3.5. | | **Bathrooms** | Whole number from 0 to 20. | | **Area (sqm)** | Whole number from 1 to 10,000 when supplied. | | **Asking price** | A valid, non-negative number, with a currency. | ## Update an existing property's details Open its board, find **Property details**, then **Edit property details**. Check the address and numeric fields, make the changes and **Save**. If details were read from a post, a note can ask you to complete the address before saving. Changing structured details is not a claim that already-published social posts were edited. Review future content and any update messages on the board; [post edits affect future sends](https://docs.lead-knight.com/en/campaigns/manage-campaign/). ## If something goes wrong - **Enter the property address**: fill the address before continuing. - **Enter a contact phone number**: correct the required phone rather than leaving a stale profile value. - **Rooms go in steps of one half (3, 3.5, 4 …)**: remove unsupported fractional room values. - **Bathrooms must be a whole number from 0 to 20**: use an integer in that range. - **The area must be a whole number of square metres**: use a whole-number area within the field's bounds. - **The property couldn't be saved. Try again.**: keep the intended changes and retry; do not assume the save succeeded. ## Related pages - [Property description and photos](https://docs.lead-knight.com/en/campaigns/property-media/) - [Property networks and sample](https://docs.lead-knight.com/en/campaigns/property-publish/) - [Campaign and Properties overview](https://docs.lead-knight.com/en/campaigns/overview/) ## Enter property details [Enter property details](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/E1/nadlanite-en-d1a11e74d8a6.mp4) 1. Start with the essential property details. Address and contact phone are enough to begin. 2. Enter the property address. 3. Add the city. 4. Add rooms, bathrooms, and size if you know them. 5. Add the asking price and currency. 6. Contact details come from your profile. Change them if this listing uses someone else. 7. Click Continue to describe the property. --- # Describe a property and choose how AI uses its photos Add property-specific instructions and media, then choose whether AI keeps, enhances or takes inspiration from your photos. Canonical: https://docs.lead-knight.com/en/campaigns/property-media/ ## What this is for After entering [property details](https://docs.lead-knight.com/en/campaigns/property-details/), give the AI the context that does not fit structured fields: distinctive features, the intended audience, tone and facts to emphasize. Then decide how the property's photos may be used. ## Before you start Check that address, price and contact facts are correct. Prepare photos and videos you have permission to publish. If the listing must show the real property without generated alternatives, choose the photo option that reflects that requirement. ## Add a description and media 1. Continue from **Property details** to the property's brief step. 1. In **About the property (optional)**, write the relevant description and instructions. The brief is optional, but details you want the AI to know should not be left for it to guess. 1. Keep the brief within 8,000 characters. Check **The AI will also use:** to understand the personal/business context being supplied. 1. Under **Media (optional)**, choose **upload media** or drag photos/videos into the upload area. 1. Wait until **Uploading…** finishes. Use the remove control on the wrong file, and **Add media** to add another file within the limit displayed. 1. If you do not want to upload media, continue without it. The AI can create images; that is not the same as using photographs of this specific property. ## Choose the photo policy When image files are attached, **What should the AI do with your photos?** offers: | Choice | What you are allowing | |---|---| | **Use my photos as they are** | Use the supplied photos rather than choosing an inspired-image mode. | | **Enhance my photos — and create more like them** | Improve photos and allow additional images inspired by them. | | **Create new images inspired by my photos** | Generate new imagery based on the photos as inspiration. | 1. Select the option that matches what may be shown in this property's marketing. 1. Review the uploaded images and your written instructions together. 1. Press **Continue** to move to [networks and the sample](https://docs.lead-knight.com/en/campaigns/property-publish/). 1. At the sample stage, inspect both the wording and the image. Check that the result represents the property accurately before creating. > **Important:** Permission to generate an image is not a guarantee that its contents are factual. Review the sample and the resulting posts before starting publication. ## Options and limits The upload area shows its current file-count limit. Wait for every selected upload to complete before continuing. A description and uploaded media are optional; the address and phone requirements belong to the preceding property-details step. Photo policy is an input to the AI workflow, not a publishing destination. Choosing it does not select Facebook groups or start posting. ## If something goes wrong - **We could not upload … You can try again.**: retry the affected file; check that it appears successfully before continuing. - **The upload is still running**: wait for completion rather than creating with an unfinished selection. - **Keep the brief within 8,000 characters to continue.**: shorten the description without removing required facts from the structured details. - The sample image could not be made: the sample may still contain text and the property can still create images. Read the exact notice; do not assume an image failure is a failed property save. - A result is not suitable: revise the brief or photo policy and inspect the next sample before creating. ## Related pages - [Property details](https://docs.lead-knight.com/en/campaigns/property-details/) - [Property networks, sample and creation](https://docs.lead-knight.com/en/campaigns/property-publish/) - [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/) ## Describe the property and add media [Describe the property and add media](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/E2/nadlanite-en-5698f7c44a54.mp4) 1. Describe what makes the property worth seeing. This step is optional. 2. Add a short description of the property. 3. The AI can also use your personal and business profile. 4. Click upload media to add property photos or videos. 5. When the description and media are ready, continue to choose networks. ## Choose how AI uses your property photos [Choose how AI uses your property photos](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/E3/nadlanite-en-d202f9a17157.mp4) 1. After uploading media, choose how the AI should use your photos. 2. Use them as they are when your photos are already ready to post. 3. Or ask the AI to enhance them and create similar images. 4. You can also create new images inspired by your photos. 5. For this property, use the uploaded photos as they are. 6. Click Continue to choose where the property is posted. --- # Choose property destinations, review the sample and create Choose where a Nadlanite property should appear, correct the AI sample and create paused content before reviewing and starting it. Canonical: https://docs.lead-knight.com/en/campaigns/property-publish/ ## What this is for This is the final part of the AI property path: choose destinations, review a sample and create the property's content. The property sequence does not include the general campaign's content-types and ideas screens. ## Before you start Complete [property details](https://docs.lead-knight.com/en/campaigns/property-details/) and [description/photos](https://docs.lead-knight.com/en/campaigns/property-media/). Connect the accounts and groups that may receive the listing. Check which profile or Page should publish, especially if several identities are connected. ## Choose where the property is posted 1. Continue to **Where to publish?**. 1. Select the networks you want. Use **Choose** to select accounts and targets; use **Edit the choice** to check or change a completed selection. 1. For **Facebook groups**, choose the publishing identity and the folders or individual groups. Read and complete the live-folder confirmation when shown: folder membership is resolved when each post goes out. 1. Review account names and target summaries. If a network is missing, follow **A network is missing? Connect it in Connections**. See [social connections](https://docs.lead-knight.com/en/channels/connect-social-accounts/) and [group connections](https://docs.lead-knight.com/en/channels/connect-facebook-groups/). 1. If Marketplace is available and selected, check the listing details prefilled from the property rather than assuming every field is complete. Availability depends on the account and workspace. 1. If a paid-ad option is shown, treat it as separate from ordinary network publishing. Review its destination and settings. Creating the property does not mean a prepared paid ad is live or approved to spend. 1. Press **Continue** to open the sample step. ## Review the sample 1. Wait while **The AI is writing a sample…**. 1. Read **A sample post about the property** and **Full text**. Check address, city, rooms, price, currency, contact details and factual claims against the actual property. 1. Inspect the sample image and the chosen photo policy. An inspired image should not be mistaken for documentary evidence of the property. 1. Write the required correction under **What should change?**, then choose **Update the sample**. 1. Review the new sample and **Changes you asked for**. Remove a change if you no longer want that instruction. 1. Use **Another image** if needed and available. Re-read the text after any change; a good image is not a substitute for accurate wording. ## Create, then review before starting 1. Read the paused-creation notice and choose **Create the property**. 1. The screen explains that creation continues in the background. Return to **Properties** or open the property board. 1. Check the posts as they become ready, including videos and each network's destination and schedule. 1. When the paused content is ready to run, choose **Resume all**. This starts the reviewed content; creating the property alone did not publish it. 1. Inspect publication outcomes on the board. Do not use the overall property status as proof that every group received the listing. ## Rules and conditional options At least one network and a sample are required. Uploads must finish. Facebook-group folders can require explicit confirmation, and messaging recipients require the consent presented in their settings. Paid-ad availability and account permissions vary. If paid-ad controls are not shown, do not assume they are enabled for your workspace. For advertising and spend approvals, use [paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). ## If something goes wrong - **No networks are connected yet.**: connect an account before selecting a publishing target. - **Pick at least one network**: select a target and complete its account/group settings. - **In the Facebook groups settings, confirm that folders are resolved when each post goes out**: reopen the group choice and complete the displayed confirmation. - **A sample is needed first** or **We couldn't create a sample. You can try again.**: wait for or retry the sample; do not assume an empty sample was approved. - **We couldn't update the sample. You can try again.**: keep the requested correction and retry before creating. - **We could not create the property. You can try again.**: retry while retaining the choices; inspect the board for any existing content. - The property is paused after creation: this is intentional. Review it and use **Resume all** when ready, not a second creation. - A group post waits for an offline extension: [repair the extension connection](https://docs.lead-knight.com/en/extension/install-and-pair/). ## Related pages - [Property details](https://docs.lead-knight.com/en/campaigns/property-details/) - [Property description and media](https://docs.lead-knight.com/en/campaigns/property-media/) - [Campaign board and outcomes](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) ## Choose where your property is posted [Choose where your property is posted](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/E4/nadlanite-en-8a0c01d1bf69.mp4) 1. After the description and photos, click Continue and choose where the property is posted. 2. Pick the office's Facebook page. Every network you connected shows up here. 3. You can also run the property as a paid ad. You control the budget. 4. Click Continue to see a sample post. ## Review the AI sample and create the property [Review the AI sample and create the property](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/E5/nadlanite-en-92ac76471709.mp4) 1. Here's how a post about the property will look, written the way the AI will write it. 2. You can see it on a phone or a desktop. 3. Want a change? Write a request and click Update the sample. 4. The property is created paused. No post goes out until you start it. 5. When the sample looks right, click Create the property. ## Start your campaign [Start your campaign](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/G6/leadknight-en-ac63b57609eb.mp4) 1. A new campaign is created paused, so nothing is published yet. 2. First review the posts on the board, and fix what you need. 3. When you are ready, click Resume all. The posts then go out on their schedule. --- # Connections and destinations Connect publishing accounts, Facebook groups and personal assistant services, and understand which connection each task needs. Canonical: https://docs.lead-knight.com/en/channels/overview/ ## What Connections is for Open **Connections** to connect the accounts and groups you use. The connected section lists existing connections; **Connect a channel** offers additional ones. **Manage** opens the controls for the selected connection. Connecting an account does not itself publish a post. A connection identifies the account that acts. A destination identifies where content goes: for example, a Facebook Page, a Facebook group or a location chosen for a post. A Facebook Page connection is not a Facebook-group connection. ## Choose the right connection | Your goal | Where to start | | --- | --- | | Publish to a supported social network | [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) | | Publish in Facebook groups and organize group folders | [Connect Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) | | Choose whether a Facebook person or Page posts in groups | [Facebook Pages and identities](https://docs.lead-knight.com/en/channels/facebook-pages-and-identities/) | | Talk to the assistant on WhatsApp, or send campaigns from your number | [Connect WhatsApp](https://docs.lead-knight.com/en/channels/connect-whatsapp/) | | Let the assistant send from Gmail or use your Google Calendar | [Connect Gmail and Google Calendar](https://docs.lead-knight.com/en/channels/connect-gmail-and-calendar/) | | Connect a desktop publishing browser | [Install and pair the extension](https://docs.lead-knight.com/en/extension/install-and-pair/) | | Use a connected cloud device for Facebook groups | [Cloud phones](https://docs.lead-knight.com/en/cloud-phones/overview/) | ## Read the status before publishing - **Connected** means a connection exists. For Facebook groups, also check the selected profile's extension or phone readiness. - **Action needed** means the connection needs attention. Open **Manage** and read the specific message. - **Not connected** means that channel is not connected yet. - **Coming soon** is not a working connect button. Availability also depends on your workspace and the platform's enabled connections. The page shows your account allowance. Do not assume every team member can connect or manage every account: ownership, role and account-sharing permissions apply. **Who can use** controls access to supported connected accounts; only the person who connected an account can change its sharing. ## After connecting Choose the actual destinations when [creating a campaign](https://docs.lead-knight.com/en/campaigns/create-manual/). For Facebook groups, review [publishing settings](https://docs.lead-knight.com/en/extension/posting-presets/): these apply to the selected profile across campaigns, not just to one post. If a connection fails to load, use **Retry** rather than treating the missing status as a confirmed disconnection. For reconnect and sign-in problems, follow the page for that connection above. ## Connect a social account [Connect a social account](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D1/leadknight-en-e932666e77ab.mp4) 1. To connect a social account, open Connections and find Connect a channel. 2. Click the network you want. Here, we connect a Facebook Page. 3. A Facebook window opens. Sign in if asked, and allow access to your Pages. 4. Back in LeadKnight, choose the Pages you want to post to. 5. Then click Connect selected. 6. The account now appears under Connected, ready for your campaigns. ## Install and connect the Chrome extension [Install and connect the Chrome extension](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D3/leadknight-en-0b9dc90e7748.mp4) 1. Facebook groups post through the LeadKnight extension in Chrome. In Connections, click Facebook groups. 2. Each Facebook profile posts from a Chrome browser that has the extension. 3. Click Install & connect. The Chrome Web Store opens in a new tab. 4. There, click Add to Chrome, then Add extension. 5. When it connects, LeadKnight shows which Facebook profile the extension posts as. ## Connect your Facebook profile and add groups [Connect your Facebook profile and add groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D5/leadknight-en-f0eff0aa4fa3.mp4) 1. To post in Facebook groups, open Facebook groups in Connections. 2. The extension found your Facebook profile. Click it to choose what to connect. 3. Tick your personal profile. Groups are posted from your profile. 4. Then click Connect selected. 5. Click Groups to see the Facebook groups of this profile. 6. Under All groups, LeadKnight lists the groups you belong to. It reads them from Facebook automatically. 7. Joined a new group? Click Sync now. 8. Or click Add group to add one by its link. 9. Use folders to organize your groups. In a campaign, you can pick a whole folder at once. ## Choose a posting pace for Facebook groups [Choose a posting pace for Facebook groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D6/leadknight-en-70cbfd779405.mp4) 1. Each Facebook profile has its own posting pace. Find Publishing settings. 2. With Automatic, LeadKnight plans the posts for you. Manual lets you set the numbers and hours yourself. 3. Then choose a pace. Safety is the most careful, with fewer posts each day. 4. Balanced gives steady reach, and Efficiency posts the most. 5. Under When to post, choose the parts of the day this profile may post in. 6. Click Save changes to apply it to all your campaigns. --- # Connect social accounts Connect supported networks, choose Pages or locations when asked, and reconnect or disconnect accounts from Connections. Canonical: https://docs.lead-knight.com/en/channels/connect-social-accounts/ ## What this connection does Social-account connections let campaigns publish through the network connection. Facebook here means Pages, not personal-profile group posting. For groups, use [the Facebook-group connection](https://docs.lead-knight.com/en/channels/connect-facebook-groups/). ## Before you start - Sign in to the network account you intend to connect and have access to its Page, profile or business location. - Check the connected-account allowance shown on **Connections**. A limit message requires resolving the allowance before adding another account. - Allow the sign-in popup to open. Keep the Connections tab available while completing the network's own authorization screens. - Use only a network offered as an active connection. A **Coming soon** tile is not available for connection; new connections can also be disabled for a platform in this workspace. ## Connect an account 1. Open **Connections**, then choose the network under **Connect a channel**. The network sign-in opens in a separate window. 1. Sign in with the intended network account and approve the access requested in that network's window. Closing it before completion does not complete the connection. 1. Return to Connections. A direct connection shows **Account connected.**; a connection needing a resource choice shows **Finishing connection…** and opens **Choose what to connect**. 1. If the picker opens, choose the intended resources and press **Connect selected**. At least one selection is required. Already-connected resources are marked **Already connected**. 1. Check that the account appears in the connected list with **Connected**. Select its exact destination in your campaign rather than assuming connection chooses every publishing target. ## Network-specific choices | Network | What happens after the network sign-in | | --- | --- | | Instagram | The account connects without an additional resource picker. | | Facebook | Select the Pages you manage; several Pages can be selected. Facebook must share at least one managed Page. | | TikTok | The account connects without an additional resource picker. | | X | The account connects without an additional resource picker. | | LinkedIn | Select one available profile or organization resource for this connection. | | YouTube | The account connects without an additional resource picker. | | Pinterest | The account connects without a board picker. Choose a board for the post in the campaign composer. | | Google Business | Select one location. Use **Search locations** to find a location missing from the initial list. Choose the intended location for the post in the composer too. | | Reddit | The account connects without a community picker. Choose the community and post fields in the composer. | | Threads | The account connects without an additional resource picker. | Pinterest, Google Business, Reddit and Threads are marked **Beta**. Availability is determined by the actual connection buttons shown in your workspace, not by this list alone. ## Manage, reconnect and disconnect 1. In the connected list, open the network's **Manage** dialog and locate the correct account. 1. For **Expired**, **Revoked** or **Needs reconnect**, choose **Reconnect** and authorize using the original account. Reconnecting with a different account can be refused as an account mismatch. 1. To remove access, choose **Disconnect**, read **Disconnect this account?**, then confirm **Disconnect**. Destinations using this account stop working until it is reconnected. Owners, admins and the connecting person have account-management permissions; if controls are unavailable, ask the appropriate person. Sharing is separate: the account's connector chooses teammates through **Who can use**. That permission covers reading conversations and publishing from that account. ## If something goes wrong | Symptom | What it means and what to do | | --- | --- | | **You need a Facebook Page** | Create a Page on Facebook, or reconnect and edit the settings in Facebook's window to tick your existing Page. A personal profile alone does not satisfy this connection. | | **Resume selection** | The resource choice is unfinished. Resume it; if the picker says the connection expired, close it and start connecting again. | | No location in the initial Google Business list | Search using **Search locations**. If more locations exist, refine the search. | | Account allowance reached | Review the displayed allowance. Disconnect an account you no longer need or resolve the plan limit before connecting more. | | Permission error | Ask a workspace owner or admin; do not repeatedly authorize a connection you cannot manage. | | Provider billing or plan error | Follow the connection message and contact support. This is a connection-provider restriction, not an instruction to pay again in LeadKnight. | | Authorization denied or window closed | Start again and complete authorization with the correct account. | ## Related pages - [Facebook Pages and identities](https://docs.lead-knight.com/en/channels/facebook-pages-and-identities/) - [Connections overview](https://docs.lead-knight.com/en/channels/overview/) - [Create a campaign](https://docs.lead-knight.com/en/campaigns/create-manual/) ## Connect a social account [Connect a social account](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D1/leadknight-en-e932666e77ab.mp4) 1. To connect a social account, open Connections and find Connect a channel. 2. Click the network you want. Here, we connect a Facebook Page. 3. A Facebook window opens. Sign in if asked, and allow access to your Pages. 4. Back in LeadKnight, choose the Pages you want to post to. 5. Then click Connect selected. 6. The account now appears under Connected, ready for your campaigns. --- # Connect your Facebook profile and groups Link the correct Facebook identity, sync or add groups, organize folders and choose campaign destinations. Canonical: https://docs.lead-knight.com/en/channels/connect-facebook-groups/ ## What this connection does Facebook-group posting uses a connected Facebook identity and its browser extension or eligible cloud phone. Each member connects their own profile. A group in the app is a publishing destination, not a new Facebook membership: adding it does not join the group or bypass its posting rules. ## Before you start - For browser posting, use desktop Chrome with [the extension installed and paired](https://docs.lead-knight.com/en/extension/install-and-pair/). Sign in to Facebook in that same Chrome profile. - For a cloud connection, finish [sign-in on the phone](https://docs.lead-knight.com/en/cloud-phones/sign-in/). - Confirm the profile or Page that should post. Access to a group depends on that identity, not just on another workspace member's membership. - Additional personal profiles use the displayed profile allowance. Each profile needs its own signed-in browser/device; **+ Add profile** provides the available connection choices. ## Connect and discover your groups 1. Open **Connections** and select the Facebook-group connection. For an existing connection, choose **Manage**, then **Manage groups**. If no active extension is found, **Open extension** opens the connection controls. 1. Select the intended identity under **Facebook profiles**. Use **Manage connection** to check its extension or phone, rather than assuming another profile's connection serves it. 1. If prompted with **Choose your Facebook identities**, select the person and/or Pages that should post, then **Connect selected**. See [Pages and identities](https://docs.lead-knight.com/en/channels/facebook-pages-and-identities/). 1. Open **Groups**, then **All groups**. Your imported groups appear with group name, ID, approximate member count and status. 1. Choose **Sync now** to refresh the selected profile's groups. Groups also update automatically. Cloud import can take a while; let it finish before assuming the list is empty. ## Add a group by link or ID 1. In group management, choose **Add group**. 1. In **Group link or ID**, paste a Facebook group link or numeric ID. Group, post, permalink and group-share links are supported when the selected profile can access the group. 1. Optionally fill **Name (optional)**, up to 300 characters. This does not change the name on Facebook. 1. Choose **Add group** and wait while the app resolves the group. The resolved group is added to the list; if lookup fails, correct the cause shown before trying again. **Not confirmed yet** means the app has not seen the group in this profile's Facebook group list. It is not confirmation of membership or permission to post. ## Find and organize groups Use **Search groups**, **Minimum members**, **Maximum members** and the size/name sort controls to find groups. Member counts are Facebook's rounded, last-observed values, not a live exact census. Unknown sizes are shown as **Unknown**; a valid member-count bound excludes them. Bounds are inclusive, non-negative whole numbers. An invalid or reversed range is not applied until corrected. **Clear filters** clears the filters, not your selections. 1. Open **Folders**, then **Create folder**. 1. Enter **Folder name**, select groups belonging to this profile and choose **Save**. 1. Use **Folder actions** for **Rename**, **Edit groups** or **Delete folder**. A group may belong to more than one folder. > **Important:** Folders stay linked to campaigns. Edits by anyone with access to the profile change future publishing destinations, not posts already prepared for sending. Deleting a folder stops future use of that folder; the groups and past publications remain. In a campaign, select individual groups or linked folders. A direct group selection remains selected even when folder membership changes. Review the folder consent before approving publishing. A post can target up to 2,000 Facebook groups; filters do not reduce the number of selected targets just because some are hidden. ## Remove or restore groups In **All groups**, select the visible groups you intend to remove and use the removal action. Removing groups hides them and prevents publishing to them in the app; it does not leave them on Facebook. Open **Removed groups** and choose **Restore** to return a group to its folders and posts. Check the confirmation's selected group count before removing. ## If something goes wrong | Symptom | Cause and next step | | --- | --- | | No groups after connection | Verify the selected Facebook identity, open its signed-in Facebook session, then **Sync now**. Cloud imports may still be running. | | Group lookup unavailable | Connect an updated extension or, where offered, a ready cloud profile for this identity. | | Profile cannot access the group | Check its Facebook sign-in and membership. Adding a link does not grant access. | | Signed-in identity does not match | Return Facebook to the linked identity, or manage the correct connection before retrying. | | Profile is busy | Wait for the current activity to finish, then retry lookup. | | **Held** with the offline-extension explanation | Reconnect the extension. The queued post goes out automatically; do not publish it again. | | **Needs verification** or a message that the post may have landed | Check the actual group before retrying, to avoid a duplicate. This is not proof of failure. | | Waiting for group-admin approval | Wait for the group administrator; repeated publishing is not the remedy. | ## Related pages - [Posting pace and schedules](https://docs.lead-knight.com/en/extension/posting-presets/) - [Install and pair the extension](https://docs.lead-knight.com/en/extension/install-and-pair/) - [Create a campaign](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Connections overview](https://docs.lead-knight.com/en/channels/overview/) ## Install and connect the Chrome extension [Install and connect the Chrome extension](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D3/leadknight-en-0b9dc90e7748.mp4) 1. Facebook groups post through the LeadKnight extension in Chrome. In Connections, click Facebook groups. 2. Each Facebook profile posts from a Chrome browser that has the extension. 3. Click Install & connect. The Chrome Web Store opens in a new tab. 4. There, click Add to Chrome, then Add extension. 5. When it connects, LeadKnight shows which Facebook profile the extension posts as. ## Connect your Facebook profile and add groups [Connect your Facebook profile and add groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D5/leadknight-en-f0eff0aa4fa3.mp4) 1. To post in Facebook groups, open Facebook groups in Connections. 2. The extension found your Facebook profile. Click it to choose what to connect. 3. Tick your personal profile. Groups are posted from your profile. 4. Then click Connect selected. 5. Click Groups to see the Facebook groups of this profile. 6. Under All groups, LeadKnight lists the groups you belong to. It reads them from Facebook automatically. 7. Joined a new group? Click Sync now. 8. Or click Add group to add one by its link. 9. Use folders to organize your groups. In a campaign, you can pick a whole folder at once. --- # Facebook Pages and posting identities Distinguish a Facebook Page's social connection from a Page or person posting in groups, and choose the correct identity. Canonical: https://docs.lead-knight.com/en/channels/facebook-pages-and-identities/ ## Two different uses of a Page A Page connected through the Facebook social-network sign-in publishes to the Page destination. A Page selected under your connected Facebook profile is an identity that can publish in eligible Facebook groups using that profile's connected device. Connecting one does not mean the other has been selected. ## Before you start For a Page-feed connection, have a Facebook Page you manage and use [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/). For group posting, connect your own Facebook login using [the extension](https://docs.lead-knight.com/en/extension/install-and-pair/) or [cloud sign-in](https://docs.lead-knight.com/en/cloud-phones/sign-in/). Keep access to the Page in Facebook. ## Choose identities for group posting 1. Open **Connections**, the Facebook-group connection's **Manage groups**, then select the relevant profile. 1. Open **Manage Pages**. During first setup, **Choose your Facebook identities** can open as part of the connection flow instead. 1. Wait for **Reading your Facebook Pages…**. Each available identity is labelled **Profile** or **Page**; inspect its name before selecting it. 1. Tick the person and/or Pages that should be available for posting. A Page marked **Connected through {name}** belongs to another member's connected login and cannot be selected through yours. 1. Press **Connect selected**. Use the resulting identity's tab for its groups and publishing settings, and select that identity when preparing the campaign. **Facebook Pages don't use a personal-profile slot.** Enabling another personal profile is still subject to your allowance. It is possible to use the login to serve selected Pages without enabling that person as a posting identity. ## Refresh Pages from a cloud phone Where the cloud controls are offered, a ready phone with an outdated identity list can show **Read Pages from the cloud phone**. Choose it and wait for the refreshed list; the UI warns that startup takes about 3–5 minutes. Review and save the identity selection afterwards. If the phone has switched into a Page without a completed identity choice, **Choose who posts** must be completed before cloud posting continues. ## Rules and permissions - Selecting a Page does not override a group's rules. Some groups do not permit Page posting; remove that group from the Page's campaign or check the group's requirements. - Each selected identity has its own group list and publishing settings. The browser connection belongs to the Facebook login serving it. - **Who can use** shares account access with selected workspace members. Selecting a Page is not the same as granting a teammate permission. ## If something goes wrong | Symptom | What to do | | --- | --- | | **You need a Facebook Page** in social-network connection | Create a Page, or reconnect and tick the Page in Facebook's authorization settings. | | Page list is stale | Open Facebook in the paired browser and retry; use the offered cloud refresh for a ready cloud connection. | | **Page not available** | Check that the serving login still has access to that Page, then review **Manage Pages**. | | Page connected through another member | Use that existing connection with permission, or ask the connector to manage it. Do not pair onto their personal profile. | | Facebook account switched in Chrome | Switch Facebook back to the connected login. Posts for that profile wait while the browser is signed in as someone else. | | Page cannot post in a group | Check the group's Page-posting rules or remove the destination; reconnecting cannot grant permission the group does not allow. | ## Related pages - [Connect Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) - [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) - [Publishing settings](https://docs.lead-knight.com/en/extension/posting-presets/) ## Connect a social account [Connect a social account](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D1/leadknight-en-e932666e77ab.mp4) 1. To connect a social account, open Connections and find Connect a channel. 2. Click the network you want. Here, we connect a Facebook Page. 3. A Facebook window opens. Sign in if asked, and allow access to your Pages. 4. Back in LeadKnight, choose the Pages you want to post to. 5. Then click Connect selected. 6. The account now appears under Connected, ready for your campaigns. ## Connect your Facebook profile and add groups [Connect your Facebook profile and add groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D5/leadknight-en-f0eff0aa4fa3.mp4) 1. To post in Facebook groups, open Facebook groups in Connections. 2. The extension found your Facebook profile. Click it to choose what to connect. 3. Tick your personal profile. Groups are posted from your profile. 4. Then click Connect selected. 5. Click Groups to see the Facebook groups of this profile. 6. Under All groups, LeadKnight lists the groups you belong to. It reads them from Facebook automatically. 7. Joined a new group? Click Sync now. 8. Or click Add group to add one by its link. 9. Use folders to organize your groups. In a campaign, you can pick a whole folder at once. --- # Connect WhatsApp for the assistant or campaign sending Understand the two separate WhatsApp connections, link your phone to the assistant, or connect your own sending number through Chrome. Canonical: https://docs.lead-knight.com/en/channels/connect-whatsapp/ ## Choose the right WhatsApp connection **Assistant on WhatsApp** links your phone so you can message the assistant. **WhatsApp · Your number** connects your own WhatsApp Web account for campaign messages to contacts and groups. These are separate connections: linking the assistant does not enable campaign sending, and connecting a sending number does not link the assistant. ## Before you start For the assistant, the workspace must have the assistant's WhatsApp channel available; the connection may show that a verified WhatsApp Business number is required. This is not an instruction to register your personal sending number as the assistant's business number. For campaign sending, use your own desktop Chrome with the [extension connected](https://docs.lead-knight.com/en/extension/install-and-pair/), your phone to sign in to WhatsApp Web, and recipients who agreed to hear from you. The workspace owner must enable sending first. Each user can connect one sending number per workspace. > **Important:** WhatsApp does not allow automated sending from regular accounts and may restrict or ban a number. Pacing does not remove that risk. Read and accept the displayed risk notice only if you understand it; you remain responsible for WhatsApp and Meta's terms and recipients' consent. ## Link your phone to the assistant 1. Open **Connections**, then **Assistant on WhatsApp**. 1. Choose **Connect WhatsApp**. The card shows a linking code and the instruction to send it to the assistant. 1. Use **Open WhatsApp** and send that code to the assistant from the phone number you want to link. Copying the code alone does not link the phone. 1. Wait for **Linked** on the card. The code expires in 10 minutes; if it expires, start again for a fresh code. 1. To stop the link, choose the assistant card's **Disconnect**. This is separate from disconnecting a campaign-sending number. ## Connect your own campaign-sending number 1. On **Connections**, choose **WhatsApp · Your number**. If sending is off, the owner must complete **Turn on WhatsApp sending?** and its acknowledgement first; other members are directed to ask the owner. 1. Read the personal risk notice in **Connect your WhatsApp** and tick **I accept this risk for my own number.** 1. Follow **Open WhatsApp Web** in the same Chrome browser as the connected extension. If the extension is not linked to your account in this Chrome, complete the displayed pairing step first. 1. In WhatsApp Web, scan the QR code with your phone if asked. Wait while the extension checks the signed-in account. 1. In **Is this your number?**, inspect the number. Choose **Yes, connect** only for your own intended number. For a different number, choose **Not my number**, sign out of WhatsApp Web, sign in correctly and retry. 1. After **WhatsApp connected.**, review any offered audience-import choices. Keeping people as audiences does not automatically make them CRM contacts. Keep WhatsApp Web open while campaign messages are sending. The connecting member's browser performs the send even when a teammate has been granted use of the number. ## Manage the sending connection - **WhatsApp Web open** means the browser can see that WhatsApp session; **Computer offline** means sends need the computer/browser connection restored. - **Pause** stops this number; **Resume** resumes it. Workspace **Stop all sending** affects contact and group sends from every number, and **Resume sending** allows them to continue. - The connector uses **Who can post** to grant eligible teammates access to the number. - **Sending rules** apply to contact and group sends from that number. You can set slower hourly/daily limits, delays and sending hours; empty pacing fields keep the automatic pace. You can only make it slower. Review the workspace time zone displayed in the dialog. - **Disconnect** removes the number from future contact/group campaign sending; existing send history remains visible. ## If something goes wrong | Symptom | What to do | | --- | --- | | Assistant code never becomes **Linked** | Send the current code to the assistant from the intended phone; check its expiry and regenerate if needed. | | Sending is off | Ask the workspace owner to enable it and complete the risk acknowledgement. Assistant linking does not enable it. | | Waiting for the extension | Pair the extension in this Chrome to your own account, not another member's browser. | | WhatsApp Web is not open or cannot be reached | Open it in this Chrome; reload the WhatsApp Web tab if the message requests it. | | WhatsApp Web is open elsewhere | Follow the message to use the current session in the WhatsApp Web tab. | | Number does not match | Sign out of WhatsApp Web and sign in to the correct number before confirming. | | **Computer offline** | Restore the connecting member's browser and WhatsApp Web session. Another member being online does not replace that connection. | ## Related pages - [Assistant](https://docs.lead-knight.com/en/assistant/overview/) - [Extension setup](https://docs.lead-knight.com/en/extension/install-and-pair/) - [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/) - [Connections](https://docs.lead-knight.com/en/channels/overview/) --- # Connect Gmail and Google Calendar Add email addresses for sending, choose the assistant's default sender, and select the personal Google calendars to sync. Canonical: https://docs.lead-knight.com/en/channels/connect-gmail-and-calendar/ ## What these connections are for Gmail lets the assistant send from a connected address. Google Calendar lets the assistant see your selected calendars and book meetings. They are separate service connections: connecting Gmail does not select calendars, and connecting a calendar does not grant email sending. ## Before you start Use a Google account you control and complete Google's sign-in and permission screens. Email sending and calendar sync must be enabled for your workspace. If the dialog says **Turn on email sending before you connect Gmail.** or **Turn on calendar sync before you connect Google Calendar.**, the service is not ready for connection in this workspace; retrying Google sign-in alone will not enable it. ## Connect Gmail 1. Open **Connections**, then **Gmail** and **Connect Gmail**. 1. Complete the Google sign-in and allow sending from the intended account. Return to the app and check that the address is listed. 1. To add another address, choose **Connect another address** and complete the same process for that Google account. 1. On the address you want the assistant to use, choose **Send from this address**. The confirmation line becomes **The assistant sends from this address.** Other connected addresses show **Connected.** 1. To share a sending address with eligible teammates, open **Who can send** and choose them. A shared address shows who shared it with you; the owner must restore the connection if it becomes unavailable. Only you and teammates you explicitly allow can send from these addresses. Connecting an address is not itself an instruction to send mail. ## Connect Google Calendar 1. Open **Connections**, then **Google Calendar** and **Connect Google Calendar**. 1. Complete Google's authorization for the correct account. Check the account email in the returned card. 1. Choose **Choose calendars**. In **Which calendars should sync?**, tick the calendars you want read and choose **Save**. 1. Check **Syncing: {names}** on the card. **No calendars are syncing yet.** means the connection exists but no calendars are selected. 1. Use **Connect another account** if another Google account is needed, then choose its calendars too. Only the calendars you select are read. The connection is personal: **Only you can see this calendar.** It is not automatically shared with your workspace. ## Reconnect or disconnect For Calendar, choose **Reconnect** when access has ended, then revisit **Choose calendars**. For Gmail, connect the address again if access ended or if the app says permission to send mail was not granted. Allow the missing sending permission in Google's flow. To disconnect Gmail, use **Disconnect** and confirm **Disconnect this address?** The assistant stops sending from it. Your mailbox and already-sent mail are unchanged. To disconnect a calendar, use **Disconnect** and confirm **Disconnect this calendar?** The assistant stops seeing the schedule and booking through it. Events in Google Calendar are not deleted. Disconnecting one service should not be mistaken for deleting your Google account. ## If something goes wrong | Symptom | Cause and next step | | --- | --- | | Connection did not finish | Start again, complete Google authorization and return to the app. | | Gmail connected without send permission | Connect again and allow sending. A connected badge alone does not resolve missing permissions. | | Shared email address unavailable | Ask the person who connected it to connect it again. | | No calendar events available after connection | Open **Choose calendars** and make sure the intended calendars are selected. | | Google is busy | Wait a minute and retry the calendar picker. | | Calendar access ended | Reconnect, then select calendars again. | | Address/calendar list may be out of date | Refresh the connection data before relying on the displayed list. A failed refresh is not proof of disconnection. | | Service turned off | New provider actions are unavailable, but the app still allows disconnecting an existing connection. | ## Related pages - [Assistant](https://docs.lead-knight.com/en/assistant/overview/) - [Calendar](https://docs.lead-knight.com/en/calendar/overview/) - [Connections overview](https://docs.lead-knight.com/en/channels/overview/) --- # Chrome extension and browser posting Understand the extension's role, its Chrome permissions and the difference between connecting a browser and linking a Facebook identity. Canonical: https://docs.lead-knight.com/en/extension/overview/ ## What the extension does The extension connects your own Chrome browser to LeadKnight and performs publishing work you approve using your signed-in accounts. It is the browser connection for Facebook-group posting. It also supports campaign sending through your own WhatsApp Web session; that number needs its [separate sending connection](https://docs.lead-knight.com/en/channels/connect-whatsapp/). The backend manages the campaign and publishing jobs. The extension performs work and reports results; installing it is not a publishing approval and does not by itself select campaign destinations. ## Setup and everyday use - [Install and pair](https://docs.lead-knight.com/en/extension/install-and-pair/): use the Chrome Web Store, connect the browser and check status. - [Posting presets](https://docs.lead-knight.com/en/extension/posting-presets/): choose Automatic or Manual settings, posting times and the available device choices. - [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/): confirm the identity, sync groups and organize folders. - [Cloud phones](https://docs.lead-knight.com/en/cloud-phones/overview/): understand the separate connected device where that feature is offered. ## Why Chrome asks for permissions Chrome may use broad wording for permissions. These are the extension's specific uses: | Permission | Purpose | | --- | --- | | `storage` | Keep the installation's pairing credential and connection/session state in Chrome. This is necessary to recognize the paired installation. | | `alarms` | Wake the extension's background worker for scheduled connection and job checks. | | `scripting` | Run the bridge used to read the signed-in Facebook identity and operate the approved publishing flow on Facebook. | | `declarativeNetRequest` | Apply the Facebook-specific request rule that supplies the expected Origin header for the user's posting requests. | | `debugger` | Perform reliable interactions with the user's Facebook posting tab, especially for photo/video publishing, using Chrome's debugging protocol. It is not permission for a support person to browse your computer. | | Facebook site access | Identify the signed-in Facebook account and carry out approved posting work in that session. | | WhatsApp Web site access | Connect the sending number and carry out approved campaign sends through WhatsApp Web. | When the debugging connection is attached, Chrome shows a bar at the top of the window saying that **"LeadKnight" started debugging this browser** (the exact wording follows your Chrome language). The permission justification scopes debugging to the Facebook tab used for publishing, not arbitrary tabs or unrelated browsing traffic. Do not dismiss the message by assuming a connection problem; check whether approved publishing is running. For WhatsApp campaign sending, the product scope is outgoing messages and group synchronization, not reading or storing incoming replies. The assistant's WhatsApp connection is separate. ## Connection is not identity or delivery proof The extension popup shows **Status**, **Last post** and, when available, **Posting as**. A browser can be paired while its Facebook identity still needs linking, or while Facebook is signed out. Check both the extension state and the identity in **Connections**. A post marked **Needs verification** is not confirmed as delivered or failed. Check the group before retrying. If the extension is offline and the result says the queued post will go out after reconnection, restore the connection rather than publishing a duplicate. ## Privacy and account responsibility Pairing authenticates this browser to your workspace; it does not transfer ownership of your Facebook account to another teammate. Read [the privacy policy](https://lead-knight.com/privacy) before granting access. Account permissions and publishing approvals still apply, and you remain responsible for the platform's terms. ## Install and connect the Chrome extension [Install and connect the Chrome extension](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D3/leadknight-en-0b9dc90e7748.mp4) 1. Facebook groups post through the LeadKnight extension in Chrome. In Connections, click Facebook groups. 2. Each Facebook profile posts from a Chrome browser that has the extension. 3. Click Install & connect. The Chrome Web Store opens in a new tab. 4. There, click Add to Chrome, then Add extension. 5. When it connects, LeadKnight shows which Facebook profile the extension posts as. ## Connect your Facebook profile and add groups [Connect your Facebook profile and add groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D5/leadknight-en-f0eff0aa4fa3.mp4) 1. To post in Facebook groups, open Facebook groups in Connections. 2. The extension found your Facebook profile. Click it to choose what to connect. 3. Tick your personal profile. Groups are posted from your profile. 4. Then click Connect selected. 5. Click Groups to see the Facebook groups of this profile. 6. Under All groups, LeadKnight lists the groups you belong to. It reads them from Facebook automatically. 7. Joined a new group? Click Sync now. 8. Or click Add group to add one by its link. 9. Use folders to organize your groups. In a campaign, you can pick a whole folder at once. ## Choose a posting pace for Facebook groups [Choose a posting pace for Facebook groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D6/leadknight-en-70cbfd779405.mp4) 1. Each Facebook profile has its own posting pace. Find Publishing settings. 2. With Automatic, LeadKnight plans the posts for you. Manual lets you set the numbers and hours yourself. 3. Then choose a pace. Safety is the most careful, with fewer posts each day. 4. Balanced gives steady reach, and Efficiency posts the most. 5. Under When to post, choose the parts of the day this profile may post in. 6. Click Save changes to apply it to all your campaigns. --- # Install and connect the Chrome extension Install the store extension, connect automatically or with a code, link Facebook and understand offline status and updates. Canonical: https://docs.lead-knight.com/en/extension/install-and-pair/ ## What you are connecting Pairing links this Chrome installation to your account and workspace. Facebook identity linking then identifies the person or Pages that may post through it. A successful pairing message is not enough if Facebook has not been linked. ## Before you start Use Chrome on your computer, signed in to the intended LeadKnight account and workspace. Facebook-group connection is not performed from a phone browser. Each personal Facebook profile needs its own browser/device where that profile is signed in. Do not pair your installation to somebody else's profile. ## Install and connect automatically 1. Open **Connections**, the Facebook-group connection and its connection controls. Choose **Install & connect** or **Install the extension** where offered. The official Chrome Web Store listing opens in a new tab. 1. Install the extension from that listing, reviewing Chrome's permission request. Return to the app tab. The app waits for the installation and attempts to connect automatically. 1. If using the extension popup instead, choose **Connect to LeadKnight**. It opens the app's connection page at `/connect-extension`; sign in if needed. 1. If the connection page shows **Connect**, choose it. While it connects, the page displays **Connecting your extension…**. 1. Open Facebook in this same Chrome profile and sign in to the intended account. **Sign in to Facebook in this Chrome — we'll finish automatically.** means Facebook identity discovery is still waiting. 1. When offered, review **Choose your Facebook identities**, then **Connect selected**. Check the displayed name and **Posting as** in the popup before preparing publishing work. 1. The connection page shows **Connected as {name}**; **Continue to LeadKnight** returns to the app. In Connections, inspect the selected profile's connection rather than only relying on the install having finished. ## Use a code if automatic connection fails 1. In the Facebook-group connection controls, choose **Enter a code instead** and copy the current code with **Copy**. 1. Click the extension icon in the Chrome profile you want to connect, then **Connect with a code**. The extension's popup and options currently use English labels even when the app is Hebrew. 1. Paste into **Connection code**, then choose **Connect**. Wait for **Connected** or read **Couldn't connect**. 1. Return to Facebook and the app to finish identity linking and selection. If pairing was accepted but the extension has not checked in, keep Chrome open and use the app's retry action. If this browser is already connected to a different profile or workspace, use the intended Chrome profile and manage the existing connection rather than overwriting another person's connection accidentally. ## Check online status | Where | What to look for | | --- | --- | | Extension popup | **Online**, **Offline** or **Not connected**, plus **Last post** and **Posting as** when available. | | Connections | The selected profile's extension strip and **Manage connection**. | | Popup **Settings** | **Technical details** contains **Last heartbeat**, **Last job** and **Last error** when support needs diagnostics. | **Online** reflects recent check-ins, not proof that a particular post succeeded. **Extension connected — Facebook identity not linked yet** requires opening Facebook in the paired browser. If Facebook was already open before installation, navigate it again when appropriate so the extension can read the identity; save unfinished Facebook work first. ## Keep the publishing browser available Keep Chrome open and the Facebook session signed in while browser work is due. **My browser only** means posts wait if the extension is offline. The app describes **Orbit 1** as working with the Facebook tab in the background and **Orbit 2** as needing Facebook in front; there is no universal foreground requirement for every method. Do not close the browser assuming a paired status alone will perform the work. For WhatsApp sending, keep WhatsApp Web open too. ## Updates The store extension receives Chrome Web Store updates. Current versions can apply an available update without restarting Chrome, after pairing and running posting/sending work have finished. Closing the extension popup/options page when it is no longer needed avoids holding up an update. Older versions before 1.5.0 need Chrome fully closed and reopened to install updates; do this when no publishing is running. ## If something goes wrong - **Offline** or **Extension not running**: open the paired Chrome profile, confirm the extension is enabled and Facebook is signed in. Queued posts with an offline explanation wait for reconnection; do not republish them. - **Not connected** or **Not paired**: complete the app connection or code flow in the correct workspace. - Identity not linked: open Facebook in that Chrome and inspect the popup's specific warning. - Waiting to switch Facebook: sign in as the linked profile. Another account in that browser cannot silently publish as the old one. - Profile limit or seat message: resolve the displayed profile allowance or **Set up your seat** before retrying. - **Needs verification** after a post: inspect the group before any retry; uncertainty is not permission to publish a duplicate. Disconnecting the extension signs out all its paired installations and requires a new pairing code. The confirmation says your Facebook account, groups and posts remain untouched. Disconnecting a Facebook profile is a different action that stops publishing from that identity. ## Related pages - [Extension role and permissions](https://docs.lead-knight.com/en/extension/overview/) - [Posting presets](https://docs.lead-knight.com/en/extension/posting-presets/) - [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) - [WhatsApp connections](https://docs.lead-knight.com/en/channels/connect-whatsapp/) ## Install and connect the Chrome extension [Install and connect the Chrome extension](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D3/leadknight-en-0b9dc90e7748.mp4) 1. Facebook groups post through the LeadKnight extension in Chrome. In Connections, click Facebook groups. 2. Each Facebook profile posts from a Chrome browser that has the extension. 3. Click Install & connect. The Chrome Web Store opens in a new tab. 4. There, click Add to Chrome, then Add extension. 5. When it connects, LeadKnight shows which Facebook profile the extension posts as. --- # Choose a Facebook-group posting pace Configure Automatic or Manual publishing, compare Safety, Balanced and Efficiency, and set posting times for each Facebook identity. Canonical: https://docs.lead-knight.com/en/extension/posting-presets/ ## What these settings control **Publishing settings** determines how often and when the selected Facebook identity posts in groups across all campaigns. It is not the schedule for only the campaign you last opened. One publication means one post in one group. ## Before you start Connect [your Facebook identity and groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/). Check its extension or phone readiness and select the correct profile/Page before editing. The estimated number of daily publications depends on the selected hours, available groups and shared Facebook-account allowance; it is not a delivery promise. ## Open and save settings 1. Open **Connections**, then the Facebook-group connection's **Manage groups**. 1. Under **Facebook profiles**, select the identity whose settings should change. 1. In **Publishing settings**, choose **Automatic** or **Manual** and configure the options below. 1. Review the daily estimate, connection status and any warning. Choose **Save changes**. 1. Wait for **Publishing settings saved. Future publications were updated.** Future publications are replanned; anything already publishing continues. Changing profiles with unsaved edits opens **Unsaved changes**. Choose **Stay**, **Discard changes** or **Save changes** deliberately. ## Automatic mode Choose a preset and at least one part of the day under **When to post**: | Preset | How the pace differs | | --- | --- | | **Safety** | The most careful pace: the longest spacing, longest same-group cooldown and fewer daily posts. Periodic rests occur more frequently. | | **Balanced** | A middle pace with less spacing and a shorter same-group cooldown than Safety, plus less-frequent periodic rests. | | **Efficiency** | The fastest pace and highest daily volume of the three, with shorter spacing and same-group cooldown. It has no preset periodic-rest rule. The app recommends Safety or Balanced. | LeadKnight's **Safety** preset uses trusted input events dispatched through the Chrome DevTools Protocol—the reason for the extension's debugger permission—together with a humanized behavior model, which other automatic posters do not. > **Important:** Safety is our most careful setting, but no setting can guarantee complete safety. You're responsible for your account's safety and for following the platform's terms. **Morning**, **Noon**, **Evening**, **Night** and **Before dawn** select the permitted parts of the day. Night crosses midnight. Under **Additional settings**, **Rest day** stops posting before the selected rest day and resumes that evening; it is not simply a midnight-to-midnight pause. Safety and Balanced can share the Facebook login's daily allowance with its other profiles and Pages; the UI shows **Your share** when this applies. Newly connected profiles also have a more conservative allowance that changes as the connection becomes established. Read the estimate shown for the actual profile instead of multiplying a nominal hourly pace by the clock. ## Manual mode Manual mode gives direct control over the target, day-by-day hours and enabled browser methods; it does not use one of the three Automatic presets. 1. Set **Target publications per day** between 1 and 300. Each day's allowance may be up to 15% below that target, never above it; available groups and hours can further limit delivery. 1. In **Active hours**, select a day and turn on publishing for that day. Set **From** and **To**; use **Add hours** for another range and **Remove these hours** to remove one. 1. Enable at least one day. Each range must end after it starts, and ranges on the same day cannot overlap. 1. Under **Posting methods**, allow the connected methods you want LeadKnight to choose among. At least one connected method must be allowed. | Method | The app's guidance | | --- | --- | | **Orbit 1** | Posts from your browser even with Facebook in the background. | | **Orbit 2** | Posts from your browser the way a person would; needs Facebook in front. | | **Orbit Quick** | The fastest browser method. | Manual mode still applies pacing; setting a high target is not a guarantee that all those publications will run. ## Choose where the profile posts Where cloud options are available, **How this profile posts** offers **Extension only**, **Extension, cloud phone as backup** and **Cloud phone only**. The connection view also describes these as **Where posts run**. Device choice and publishing policy are separate controls; the posting-device choice saves immediately, while policy edits use **Save changes**. A connected phone is required for cloud publishing. **Safety never posts from the cloud phone.** The cloud cannot post video; media needing the browser must use the extension. Selecting **Scheduled verification** to use the cloud phone changes scheduled checks, not where publishing occurs; that option requires a successful cloud-phone publishing session first. ## Pause and troubleshoot **Pause publishing** pauses all Facebook-group campaigns for that identity until **Resume publishing** is used. Review the confirmation before pausing. It is not a pause of unrelated profiles. | Symptom | What to check | | --- | --- | | No daily estimate or add-groups message | Add groups for this identity. | | Cannot save Automatic | Select at least one part of the day. | | Cannot save Manual | Check target range, enabled days, non-overlapping hours and an allowed connected method. | | Posts waiting while extension is offline | Restore the paired browser; extension-only publishing waits. Do not publish the queued post again. | | Cloud selected but nothing runs | Confirm the phone is connected and signed in; Safety and video do not use the cloud. | | Facebook refusal with a resume time | Read the displayed refusal and resume time; changing to a faster preset is not a repair for the Facebook account. | | **Needs verification** | Check the actual group before retrying to avoid duplicates. | ## Related pages - [Install and pair](https://docs.lead-knight.com/en/extension/install-and-pair/) - [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) - [Cloud phones](https://docs.lead-knight.com/en/cloud-phones/overview/) - [Campaign scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) ## Choose a posting pace for Facebook groups [Choose a posting pace for Facebook groups](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/D6/leadknight-en-70cbfd779405.mp4) 1. Each Facebook profile has its own posting pace. Find Publishing settings. 2. With Automatic, LeadKnight plans the posts for you. Manual lets you set the numbers and hours yourself. 3. Then choose a pace. Safety is the most careful, with fewer posts each day. 4. Balanced gives steady reach, and Efficiency posts the most. 5. Under When to post, choose the parts of the day this profile may post in. 6. Click Save changes to apply it to all your campaigns. --- # Cloud phones for Facebook-group posting Understand the separate cloud device, connection and warmup statuses, publishing limits and the difference between publishing and verification. Canonical: https://docs.lead-knight.com/en/cloud-phones/overview/ ## What a cloud phone is A cloud phone is a separate device on which you sign in to Facebook through a screen shown in the app. The Facebook session remains on that phone. It can perform eligible Facebook-group publishing when your selected publishing-device setting allows it; it is not the same connection as the Chrome extension on your computer. Cloud-phone controls are available only where enabled for your market/workspace. If you do not see **Cloud phone** in the profile's connection options, it is not available for your workspace. The UI allows only a workspace owner or admin to connect a cloud phone. ## Where to go - [Sign in on a cloud phone](https://docs.lead-knight.com/en/cloud-phones/sign-in/): prepare the device, use its screen, handle Facebook checks and choose posting identities. - [Publishing settings](https://docs.lead-knight.com/en/extension/posting-presets/): choose browser-only, cloud backup or cloud-only publishing where offered. - [Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/): import, add and organize the selected identity's destinations. - [Pages and identities](https://docs.lead-knight.com/en/channels/facebook-pages-and-identities/): choose whether a person or Page posts from the phone's Facebook login. ## Read the phone's status | What you see | Meaning and next step | | --- | --- | | **Not set up** / **Connect a cloud phone** | No phone connection has been set up for the profile. | | **Setting up** / **Preparing the phone…** | The device is being prepared. If preparation is slow, the card says you can leave and return when the sign-in button appears. | | **Signed out** / **Sign into Facebook on the phone** | The phone needs Facebook sign-in, including when a previous sign-in expired. | | **Ready** / **The phone is connected** | A phone connection exists. Still check warmup, identity choice and the publishing settings. | | **Choose who posts** | Complete the identity selection before cloud publishing can continue. | | **Unavailable** or a connection failure | Read the reason and retry the relevant connection action. A status-load error is not itself proof of being signed out. | | **Disconnecting… This takes a few minutes.** | Sign-out and cleanup are running. A retrying message means cleanup is still being attempted. | ## Warmup is separate from connection A ready phone may show **Warming up your phone**, warmup-session progress and an approximate first-post time. After warmup, **Ramping up to full posting speed** means volume is still increasing gradually. A Facebook check may pause warmup until the displayed time. **Post now** asks for explicit confirmation before warmup finishes. The app warns that posting immediately from a brand-new phone makes Facebook more likely to ask for verification. Choosing it does not cancel the remaining warmup or the gradual posting ramp. ## Publishing-device choice and limits Creating or signing in to a phone does not by itself switch all publishing to it. Review the profile's **How this profile posts** setting. Cloud backup needs a connected phone, and **Safety** never publishes through the cloud. The cloud supports text and up to 5 JPEG, PNG, GIF or WebP photos, up to 64 MB per post. It does not publish video. A post that needs unsupported media, more photos or larger files must use the browser extension or be changed to supported media. The app's publishing result explains when nothing was sent because of such a limit. If Facebook does not offer multi-group cloud posting for the account, the publishing-settings warning says the phone posts to one group at a time at low priority and returns to normal automatically. Do not treat a connected phone as a guaranteed publication count or speed. ## Scheduled verification is another setting **Scheduled verification** can move scheduled checks from the paired extension to the cloud phone; this does not move publishing. The app requires one successful cloud-phone publishing session for that account before offering the change. Posting-device choice, verification-device choice and phone sign-in should be checked separately. ## Disconnecting and responsibility **Disconnect from cloud phone** signs Facebook out, wipes the phone's browser data and deletes the saved password. New posts from that profile stop until sign-in is restored, but a post already being sent may still finish. Groups and campaigns remain. If an automatic-disconnection date is shown, use that displayed date rather than assuming the connection lasts indefinitely. The optional saved-password disclosure recommends installing the publishing system on your computer rather than using the cloud and warns of increased blocking risk and possible errors. Read the disclosure, [privacy policy](https://lead-knight.com/privacy) and [terms](https://lead-knight.com/terms). You remain responsible for Meta's terms. --- # 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/) --- # Understand the scheduled-content calendar Read the weekly calendar, filter planned and published content, inspect Facebook-group details, and start a post for a specific day. Canonical: https://docs.lead-knight.com/en/calendar/overview/ ## What this area is for **Scheduled content** combines upcoming campaign occurrences with recorded publishing results in a weekly view. It helps answer two different questions: what is planned, and what actually happened? A future plan is not proof that a post was published. ## Pages in this area - This overview explains navigation, filters, status labels, and the Facebook-group detail windows. - [Start a post from a calendar day](https://docs.lead-knight.com/en/calendar/start-post/) explains **Add post**, the campaign picker, and checking the seeded schedule before publishing. ## Navigate the week 1. Open `/calendar`. The board shows seven days around the currently selected week and highlights today. 2. Use **Previous week** or **Next week** to move one week at a time. The date range between the arrow buttons shows the displayed week. 3. Press **Today** to return to the week containing today in the workspace time zone. 4. Inspect a day's cards. The current day's heading separates published and scheduled counts; other days show their item count. These counts follow the active filters and are not audience or engagement metrics. The week begins on Monday in English and Sunday in Hebrew. Dates and publishing times are grouped by the workspace time zone, not necessarily your device's local zone. If a post appears on an unexpected day, check [workspace time-zone settings](https://docs.lead-knight.com/en/settings/overview/) before changing its schedule. On a phone, days stack vertically and empty days are compact. When a day has more than five displayed entries, use **+{count} more** to open the complete day in a scrolling dialog. A folded group block is one displayed entry and can contain many individual records. ## Filter the board The desktop filter row offers **All channels**, **All campaigns**, and **Any status**. On a phone, open **Filter**, choose **Channel**, **Campaign**, or **Status**, then press **Show results** to close the filter window. Choices apply as you make them. | Status filter | What it includes | | --- | --- | | **Any status** | Upcoming entries and the returned past results, including failures and unconfirmed results. | | **Planned** | Upcoming occurrence entries that are not cancelled or skipped. This is a planning view, not evidence of publication. | | **Published** | Results marked **Published** or **Posted (no link yet)**; WhatsApp summaries with sent messages can also appear. | | **Skipped** | Cancelled or skipped occurrence entries. | Channel and campaign choices are based on the displayed week's data. A selected filter stays selected when you move to another week, even if it has no matching entries there. Return all three controls to their unrestricted choices before concluding the week is empty. ## Understand the cards and labels | Label or appearance | How to read it | | --- | --- | | **Planned** | An expected occurrence, including a projected future slot. Lighter or dashed entries are upcoming, not already posted. | | **Scheduled** | An occurrence with a materialized or queued record whose scheduled time has passed, as displayed by this calendar. It is not a success confirmation; inspect the actual result or campaign. | | **Published** | A recorded successful publishing outcome. **View post** opens the direct post when a link is available. | | **Posted (no link yet)** | A posting outcome recorded without a direct post link. Do not confuse the missing link with a fully verified direct URL. | | **Failed** | The recorded publishing attempt failed. Open the campaign to investigate. | | **Not confirmed** | The outcome has not been confirmed. Do not treat it as success or automatically create a duplicate post. | | **Skipped** or a cancelled entry | The occurrence will not publish as planned. A cancellation explanation may be available on the entry. | Individual upcoming cards show a time, channel, campaign name, and status; selecting one opens its campaign. Past-result cards show the destination or account, the result, a campaign link when available, and a post link when available. A result without an associated campaign can be labelled **Quick post**. WhatsApp results are grouped by send and day. Their summaries distinguish sent, failed, and not-confirmed message counts; selecting one opens the related campaign's send details. These counts are messages, not social-post engagement. ## Inspect Facebook groups Facebook-group entries are folded so the board remains readable. 1. Press an upcoming **Facebook groups** block. The summary reports planned occurrences, distinct groups, and campaigns; these are different counts. 2. In the detail window, read **Group destination**, **Scheduled time**, **Campaign**, and **Status** for each occurrence. The destination may also include the posting profile's name or identifier. 3. Select the campaign link to investigate the underlying schedule or posting setup. 4. For a past-results **Facebook groups** block, open it and inspect each group's destination, profile, time, and outcome separately. Do not use the fold's heading as proof that every row succeeded. For published group results, a direct **View post** link is shown when available. Otherwise the app may offer a link to your posts in the group, or indicate that the link is unavailable. Check the actual row and destination rather than assuming every group has a direct permalink. ## Rules and current limits - The calendar is a reading and navigation surface. It does not offer drag-to-reschedule, moving an occurrence, or skipping a post directly on the board. Open the campaign to work with its available scheduling controls. - **Add post** starts creation; it does not save or publish a post by itself. - A projected slot may change as the campaign's schedule is resolved. It is not a delivery guarantee. - Cancellation reasons can include a disconnected channel, an inactive campaign, unavailable media, or elapsed publishing permission. Some missed-time explanations explicitly say that missed slots are not published late; fix the cause and review the campaign rather than expecting automatic catch-up. ## If something goes wrong | Symptom | Meaning and next step | | --- | --- | | **No posts** | Check the displayed week and all filters. This means no matching displayed entries, not necessarily no content in the workspace. | | The scheduled-content load warning appears | Some scheduled posts may be missing. Check your connection and reload before relying on the board as a complete schedule. | | **Couldn’t load past results. Scheduled content is still shown.** | Plans are available but historical outcomes failed to load. Do not infer success or failure from the remaining planned cards. Reload to fetch the results again. | | **Showing the first results for this week** | The returned results are truncated. The week is not a complete historical report; open the relevant campaign for more detail. | | A day or time looks shifted | Check the workspace time zone and the original campaign schedule. The calendar uses workspace-local dates. | | A group looks missing | Clear filters, expand the day's additional entries, and inspect the folded **Facebook groups** block. | ## Related pages - [Start a post from a calendar day](https://docs.lead-knight.com/en/calendar/start-post/) - [Campaign scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) - [Campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Workspace time zone](https://docs.lead-knight.com/en/settings/overview/) - [Analytics and operational cards](https://docs.lead-knight.com/en/analytics/overview/) ## Read your scheduled-content week [Read your scheduled-content week](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/H1/leadknight-en-09c8212458b0.mp4) 1. Scheduled content shows what went out and what is planned, in one view. 2. You see one week at a time. 3. Move between weeks with the arrows, or jump back with Today. 4. Filter by channel, campaign, or status. 5. Lighter chips are upcoming posts that have not gone out yet. ## Start a post from the calendar [Start a post from the calendar](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/H2/leadknight-en-48d6c6d7b378.mp4) 1. To plan a post for a specific day, use that day’s plus button. 2. Click Add post. 3. Choose which campaign the post joins. 4. Here, we start a new campaign. 5. The new campaign opens, already set to that day. --- # Start a post from a calendar day Use Add post on a chosen day, select a new or existing campaign, then verify the suggested time and each network's schedule before publishing. Canonical: https://docs.lead-knight.com/en/calendar/start-post/ ## What you will do Start a post from a particular day in **Scheduled content**, choose which campaign it belongs to, and finish it in the real post composer. The calendar is an entry point, not a separate editor or a one-click publishing button. ## Before you start - Confirm the workspace and its [time zone](https://docs.lead-knight.com/en/settings/overview/). The calendar uses the workspace's local day. - Have a connected publishing account and permission to publish to the destinations you intend to select. - Decide whether the post should join an existing campaign or start a new one. Archived campaigns and campaigns still being created in the background are excluded from the picker. - Prepare the text and any required media. Different destinations can require different formats or media. > **Important:** Clicking a day seeds 10:00 on that day in the workspace time zone. It does not reserve a slot, validate that the time is still in the future, or publish anything. Always check the final schedule. ## Start from the chosen day 1. Open `/calendar`. Use **Previous week**, **Next week**, or **Today** to display the desired week. Read the date on the day itself, not just the week range. 2. Press **Add post** inside that day's column or row. The **Add a post** dialog opens and asks **Which campaign should the post join?** 3. Choose a branch: - Select the name of an existing campaign to add the post there. The manual composer opens with the calendar time passed into it; the campaign's opening questions and the creator-choice question are skipped. - Select **New campaign** to start a campaign. Answer the opening questions shown, such as **Campaign goal**, **Goal details**, **Urgency**, and, when applicable, **Leads**. Use **Continue** to advance. The calendar entry chooses the manual path rather than asking **Who creates**. 4. Confirm you reached the intended campaign's composer. The first calendar click has not saved a server-side campaign or post by itself. In the real-estate edition, the picker asks **Which property should the post join?** and offers **New property**. Existing rows are properties rather than general campaigns. The selected-day and schedule-checking rules are the same. ## Write, select networks, and verify timing 1. Under **Post content**, enter the post text and, if useful, a **Name**. Add the media you need, or use **Continue without adding media** for a text-only post where the destination supports it. After media selection or continuing without media, the network choices become available. 2. In **Networks**, choose the accounts and destinations that should receive the post. Check the selected targets, not only the network icons. Press **I'm done** to continue to **Preview**. 3. Review **Preview**. Use **Add or edit networks** if a target is missing or wrong, then press **Finish** to reach **When should the post go out?** 4. Check each selected account's schedule. For a one-time destination, the calendar supplies the chosen day's 10:00 as an initial time. Change it if needed, especially for today or a past day. Do not assume the calendar picked your business's preferred posting time. 5. For **Facebook groups**, review the publishing window. The calendar time seeds the window's start and the initial end is unset; it is not a promise to publish to every selected group at exactly 10:00. Review **Start and end dates**, the end date if required, and **Post priority** for your intended posting plan. 6. Resolve any schedule, destination, media, or consent warnings. When ready to authorize publication on the schedules shown, press **Publish to the campaign**. In the real-estate edition, the label is **Publish to the property**. To save without authorizing publication, use **Save as a draft in the campaign** or the corresponding property label instead. 7. Read the completion screen and each network's outcome. Then open the campaign or return to **Scheduled content** and the chosen week. Check the actual cards and schedule rather than treating the original day click as confirmation of publication. ## Options and rules | Choice | What it means | | --- | --- | | Existing campaign | Adds a post without re-answering the campaign's goal and urgency. Only eligible campaigns appear in the picker. | | **New campaign** | Opens campaign creation first. Nothing is saved on the server just by opening the questions. | | One-time schedule | Starts with the selected day at 10:00; you can review and change it before publishing. | | **Repeats**, where available | Uses the recurrence you configure in the composer, not an implied recurrence from clicking the calendar. Check days, time, and end condition. | | **Facebook groups** | Uses a start/end publishing window and the group's posting rules; a start time is not an exact delivery time for every group. | | Save as a draft | Saves content without publishing it. A draft is not an active scheduled send. | The schedule carried from the calendar is a starting value. Restored work or later changes can affect the final values shown in the composer. Review every selected account before the final publish action. The calendar does not support dragging a post to reschedule it. For changes to an existing post, open its campaign and use its available editing or scheduling controls; **Add post** creates new content rather than moving an old entry. ## If something goes wrong | Symptom | Cause and next step | | --- | --- | | The campaign is missing from the picker | It may be archived, still being created, or absent from the loaded workspace. Check the workspace and campaign state; opening **New campaign** is not a substitute for selecting the intended existing one. | | A time is already in the past | The calendar starts from 10:00 even when that time has passed. Pick a valid future time in the composer. | | The composer asks to fix a publishing time | One selected network's schedule is invalid or does not fit that network. Review every account's schedule, not only the first one. | | A network is missing or cannot load | Review its connection and permissions. Reload the network choices; do not publish to an incomplete selection unless that is your actual intention. | | Media is marked unavailable | Remove or upload the affected file again, then inspect the preview and targets. | | A post is saved but not scheduled | Check whether you chose the draft action. Open the campaign and review its card state and publishing schedule. | | Some networks did not publish | Read their individual completion reasons. A failed or set-aside network does not become successful because another network succeeded; fix it from the campaign before retrying. | ## Related pages - [Scheduled-content calendar](https://docs.lead-knight.com/en/calendar/overview/) - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Campaign scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) - [Campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Workspace time zone](https://docs.lead-knight.com/en/settings/overview/) ## Start a post from the calendar [Start a post from the calendar](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/H2/leadknight-en-48d6c6d7b378.mp4) 1. To plan a post for a specific day, use that day’s plus button. 2. Click Add post. 3. Choose which campaign the post joins. 4. Here, we start a new campaign. 5. The new campaign opens, already set to that day. --- # Analytics, operational cards, and paid-ad results Understand the current content-analytics unavailable state, the three live operational cards, and the optional paid-ad results, metrics, currencies, and attribution rules. Canonical: https://docs.lead-knight.com/en/analytics/overview/ ## What this area contains This overview is the guide to the Analytics area: the current content view, the three operational cards, and the paid-ad section when enabled. Paid-ad creation and account management are covered in [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). > **Important:** The content view currently shows **Analytics unavailable** and **Performance data is unavailable.** There are no content-performance KPI cards, charts, top-post rankings, channel-performance tables, or content date-range controls here. Publishing content does not currently turn this view into a performance dashboard. The operational cards below that message are real workspace information. They help you manage work; they do not measure reach, engagement, conversions, or content return on investment. ## What each operational card means ### Up next in the queue **Up next in the queue** shows up to five upcoming card runs, soonest first, from active campaigns. Each row shows a post title, campaign, channel when known, and upcoming time in the workspace time zone. - Only future next-run times on active or scheduled, non-held cards qualify. Draft, paused, held, finished, and already-past runs are not a list of upcoming work. - A row is a card's next run, not every future occurrence of a repeating schedule. This is a short preview, not the full calendar. - Select a row to open its campaign. **Open scheduled content** opens the weekly calendar. - If some campaign boards fail to load, an error warns that the queue may be incomplete. Successfully loaded rows can remain visible alongside that warning. Use **Retry**; do not interpret a partial list as the entire schedule. ### Connected channels **Connected channels** summarizes channel connection states. **Manage** opens Connections. - The green indicator means **Connected**; the warning indicator means **Action needed**. Channels that are entirely unconnected are omitted from this strip. - Official-channel states come from the connected accounts. Facebook groups use extension pairing and saved group destinations: a paired identity can appear connected, while saved groups without a paired identity require action. - This is connection status, not audience size, performance, or a guarantee that a browser is currently online and able to complete every post. Open Connections to inspect an account that needs attention. ### Active campaigns **Active campaigns** shows up to three active campaigns, ordered by their derived activity rather than by performance. Rows show the campaign name, board type when known, number of posts, channel icons, and active status. Select a row to open the campaign; **View all** opens the full campaign list. The post count is the campaign's content count, not the number of successful publications, customers reached, or leads. An active campaign is not proof of successful delivery. ## Content and Paid ads tabs When paid-ad capabilities are enabled for your workspace, Analytics shows the outer **Content** and **Paid ads** tabs. **Content** contains the unavailable performance state and the operational cards above. **Paid ads** opens a separate paid-ad management and reporting surface. If you do not see **Paid ads**, it is not enabled for your workspace yet. A capability-loading error can also prevent the tabs from appearing; resolve the displayed error and use **Retry** before concluding that access is disabled. The content view does not gain performance charts or a date picker when paid ads are enabled. ## The four paid-ad sections | Tab | What it contains | | --- | --- | | **Results** | A selectable reporting period, currency-specific metric totals, account spending and cap details, and campaign rows. | | **Lead forms** | Forms for accessible accounts on platforms that support instant forms. Rows show **Name**, **Type**, **Leads**, **Made in**, and available **Actions**. Eligible forms created in LeadKnight can offer **Make a copy**, which starts a copy for a selected post in the ad editor. | | **People & approvals** | Owned accounts and who may use them, plus **Pending approvals** you are permitted to decide. Only the account owner manages account sharing. | | **Settings** | Workspace privacy-policy settings and per-account connection, account on/off, monthly cap, tracking, and conversion-sharing controls where supported and permitted. | **Connect an ad account** opens Connections. Management actions depend on your workspace role, account ownership, account usability, platform capabilities, and the particular operation. A viewer or support-mode view is not a way to perform paid-ad mutations. Privacy-policy editing requires an owner or admin; account settings require the account owner and mutation access. Turning **Account on** to **Account off** prevents new ads; it does not pause ads already running. Do not use that switch as an emergency stop for a live ad. See [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) for the publishing and management workflow. ## Read paid results step by step 1. Select **Paid ads**, then **Results**. The starting range is the first day of the current month through today, initialized using the workspace time zone. 2. Set **From** and **To**. The start must be on or before the end. Results load for the selected range; **Retry** refreshes the results and related paid-account data. The dates include both boundary days. 3. Press **Choose metrics**, select between one and eight metrics, and press **Save**. The selection controls the currency-total cards, not the fixed columns in each campaign table. Preferences belong to your user in the current workspace. The initial defaults are **Spend**, **Leads**, **Cost per lead**, **Meetings**, **Cost per meeting**, and **ROAS**. 4. Read each **Totals · {currency}** card independently. The app groups accounts by currency; it does not convert currencies or show one mixed-currency money total. 5. Read each account card's account name and platform, **Spend this month**, **Monthly cap**, and **Last synced: {date}**. These monthly spending details are distinct from the selected reporting period. **No cap** means no monthly cap is configured, not zero spend. 6. Under **Running ads**, inspect **Ad / campaign**, **Status**, **Budget**, **Leads**, **Cost per lead**, and **Actions**. Despite the section heading, inspect each row's actual status; do not assume every listed campaign is live. The list includes ads created outside LeadKnight and marks those rows accordingly. 7. Use an available platform link or permitted row action only after checking the specific account and campaign. An unavailable budget or action can display as **—** or be absent; the screen does not invent a value or grant access. ## What the selectable metrics mean All definitions below describe paid-ad results, not organic-content analytics. | Metric | Meaning in this screen | | --- | --- | | **Spend** | Stored, synchronized platform campaign spend in the selected period and account currency. | | **Leads** | Distinct, non-deleted CRM contacts with an attributed touchpoint for the relevant ad account or campaign during the selected period. This is not simply the platform's conversion number or a form's total submissions. | | **Cost per lead** | Period spend divided by those attributed leads. Displays **—** when there are no leads. | | **Meetings** | Attributed CRM contacts with at least one stage event whose meaning is a held meeting during the period. Counts contacts, not every meeting event, scheduled appointment, or CRM task. | | **Cost per meeting** | Period spend divided by the held-meeting contact count. Displays **—** when that count is zero. | | **Won** | Attributed CRM contacts with at least one won-stage event during the period. This is event history, not merely the contact's current stage. | | **Revenue** | Stored deal values for attributed contacts with a won-stage event in the period, including only deal values matching the account currency. It is not a payments-received or invoice report. | | **ROAS** | Attributed revenue divided by spend, shown as a multiplier. It is not profit. An individual account or campaign result can be unavailable when spend is zero or currency consistency cannot be established. | | **Impressions** | The impression count synchronized from the advertising platform for the period; it is not a count of unique people. | | **Clicks** | The click count synchronized from the advertising platform for the period. | | **CTR** | Clicks divided by impressions, multiplied by 100. Displays **—** when impressions are zero. | | **Cost per click** | Spend divided by clicks. Displays **—** when clicks are zero. | | **Platform conversions** | The platform-reported conversion value synchronized for the period. It may be fractional or unavailable, and is separate from CRM leads, meetings, and wins. | Monetary costs are rounded in the account currency's smallest unit before display. **—** means the value is not available or cannot be calculated; it is not interchangeable with a reported zero. ## Attribution, dates, and currency cautions - CRM outcomes require an attributed touchpoint linked to the relevant ad account, and to the campaign when reading a campaign row. Merely having a CRM contact or a generic source label does not establish paid-ad attribution. - Leads are counted by qualifying touchpoints during the period. Meetings and wins are counted by their stage-event dates; they can belong to leads acquired before the period. This is not a single acquisition-cohort conversion funnel. - CRM event-day boundaries use the ad account's time zone. The initial date-picker range uses the workspace time zone, and platform spend uses synchronized daily records. Check time zones when comparing with an external report. - The account-level CRM counts deduplicate a contact attributed to several campaigns in that account. Adding campaign-row lead counts can therefore differ from the account count. Currency totals sum account results and are not a cross-account unique-person count. - Currency-total cards sum like-currency amounts and counts, then recompute costs, CTR, and ROAS from their numerators and denominators. They do not add individual ratios. Different currencies remain separate; there is no exchange-rate conversion or meaningful mixed-currency sum. - Revenue excludes deal values in a different currency from the account. Interpret a currency-total ROAS as the ratio of the included currency-matched amounts, not all business revenue. A total is not proof that every underlying account's attribution is complete. - Platform conversions may be attributed differently from CRM outcomes. A currency total shows platform conversions only when every included account supplies that value. - **Last synced: {date}** is a freshness indicator. Platforms can report spend with a delay of up to a few hours, so the monthly cap may be crossed slightly. Neither the cap nor a recently displayed status guarantees an instantaneous spending stop. ## If something goes wrong | Symptom | Meaning and next step | | --- | --- | | **Analytics unavailable** in Content | This is the current content-performance state, not an instruction to create more posts to unlock charts. Use the operational cards and calendar for workflow information. | | The upcoming queue has no rows | Check whether active campaigns have future, non-held active or scheduled cards. Open the calendar and campaign board; this preview is not the whole publishing history. | | A queue warning appears with some rows | One or more boards failed to load. Use **Retry** and treat the current queue as partial. | | **No visible ad accounts** | Connect your own account or ask its owner to share access. Account visibility is not the same as workspace membership. | | A date-range error appears | Enter valid **From** and **To** dates with the start no later than the end. | | **Choose metrics** is disabled or saving fails | Preferences must load first; support mode cannot change them. Use the shown **Retry** or reopen the picker after correcting the error. Keep between one and eight choices. | | Leads or revenue look lower than the platform | Check attribution, CRM stage events, selected dates, account time zone, matching deal currency, and synchronization. Platform conversions are a different measure. | | A result is **—** | Check for a zero denominator, unreported platform data, unavailable budget, or currency mismatch; do not replace it with a guessed number. | | Forms, approvals, or controls are missing | Check platform support, account ownership and sharing, workspace role, and connection status. Only permitted items and actions are shown. | ## Related pages - [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) - [Scheduled-content calendar](https://docs.lead-knight.com/en/calendar/overview/) - [Campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/) - [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) --- # Contacts and your pipeline Find contacts, switch between the table and Kanban, and see which relationships need attention. Canonical: https://docs.lead-knight.com/en/contacts/overview/ ## What this area is for **Contacts** brings together a person's details, deal stage, notes, tasks, communications and meetings. Open a row or card to work in the contact panel without leaving the list. Contacts and audience members are different: an audience is a list for reaching people together, not automatically a CRM record. ## Find the people you need 1. Open **Contacts** from the navigation. The heading shows the contact count for the current workspace. 2. Use **Search by name or phone** to narrow the list. 3. In a team workspace, choose **All** or **Mine**. Access permissions still apply; **All** does not bypass another person's privacy settings. 4. Choose **Needs attention** to focus on contacts with signals such as **Awaiting first reply**, **Upcoming task overdue**, **Idle** or **No upcoming task**. The attention bar also reports pending requests and other relevant issues. 5. Switch between **Table** and **Kanban**. On a phone, the table option presents contact cards. Kanban groups contacts by their configured stage; scroll sideways to see more stages. 6. Open a contact to inspect its details and choose your next action. In Nadlanite, **Buyer** and **Seller** filters and an **Exclusivity ending** filter also appear. Team attention can include **Owner left the team**; that filter is not the same as your ordinary personal list. ## Work with the table The table is grouped by stage, and stage groups can be collapsed. Click a sortable heading, such as **Contact**, **Upcoming task** or **Last contact**, to sort ascending; click again for descending and once more to clear the sort. Empty or hidden values stay at the end in either direction. Scroll sideways when the table has more columns than fit on-screen. The contact column stays visible as you browse the other fields. Use controls inside a cell for their specific action; click the record itself to open the full contact panel. Workspace-configured custom columns can also appear, so two workspaces need not have identical tables. ## Choose a guide | Your goal | Detailed instructions | | --- | --- | | Create one record | [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) | | Bring in a spreadsheet | [Import contacts](https://docs.lead-knight.com/en/contacts/import-contacts/) | | Change a deal stage | [Move through the pipeline](https://docs.lead-knight.com/en/contacts/move-through-stages/) | | Rename and arrange stages | [Customize stages](https://docs.lead-knight.com/en/contacts/customize-stages/) | | Update information and tags | [Edit details and tags](https://docs.lead-knight.com/en/contacts/details-and-tags/) | | Write an internal note | [Notes](https://docs.lead-knight.com/en/contacts/notes/) | | Plan the next action | [Follow-up tasks](https://docs.lead-knight.com/en/contacts/follow-up-tasks/) | | Record a conversation | [Calls, messages and history](https://docs.lead-knight.com/en/contacts/communication-history/) | | Arrange a video meeting or invitation | [Meetings](https://docs.lead-knight.com/en/contacts/meetings/) | | Record a seller's property in Nadlanite | [Seller's property](https://docs.lead-knight.com/en/contacts/seller-property/) | ## Permissions and list actions Viewers do not see **New contact**. **Import** and **Export** are available to workspace owners and admins. **Export** offers **Excel file (.xlsx)** and **CSV file**. Stage customization is also an owner/admin action; a team member's settings access can instead lead to privacy settings. A contact can have different permissions for its card, deal, tasks, notes, communications and meetings. A visible record does not mean every section is editable. A frozen contact also restricts changes. ## If something goes wrong - **No contacts yet**: check the workspace and filters before adding or importing records. - **Could not load contacts**: use **Retry** in the affected error message. - A known contact is missing: clear the search and attention filters, then check **All** versus **Mine** and your access permissions. - A stage appears as **Stage private**: deal-stage access is restricted; it is not an unnamed pipeline column. ## Related pages - [Audiences](https://docs.lead-knight.com/en/audiences/overview/) - [Calendar](https://docs.lead-knight.com/en/calendar/overview/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) ## Contacts at a glance [Contacts at a glance](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J1/nadlanite-en-72a3987221bb.mp4) 1. Contacts is your CRM: everyone you work with, in one list. 2. The attention bar shows who is waiting for a reply, has an overdue task, or needs a next step. 3. Search by name or phone. 4. Filter to show only buyers, or only sellers. 5. Switch to Kanban to see contacts by stage. 6. Click any contact to open their record. --- # Add a contact Create a contact with the details your workspace requires, choose a stage and optionally add a follow-up task. Canonical: https://docs.lead-knight.com/en/contacts/add-contact/ ## What this does **New contact** creates one CRM record. Use it when you need a place for a person's details and follow-up work, rather than importing a whole spreadsheet. ## Before you start - Select the correct workspace and open **Contacts**. - You need a role other than viewer to see **New contact**. - Prepare a **Name** and the **Required contact details** stated at the top of the dialog. Your workspace can require **Phone**, **Email**, **Phone and email**, or **Phone or email**. ## Add the record 1. Click **New contact**. The dialog explains which contact details are required. 2. Fill in **Name**, then **Phone** and/or **Email** as required. Leaving the phone or email field runs a duplicate check. 3. Choose **Stage**. Only nonterminal stages are offered when creating a contact. The initial selection is the first such stage, or the stage from which you opened the add action. 4. If you are an owner or admin in a team workspace, choose **Owner**. The list excludes viewers and initially selects you. 5. Optionally choose **How they found us** and fill in **Source details**. Leaving the source unselected records it as unknown. 6. Optionally fill in **Upcoming task** and **Due** together. To save without a task, leave both empty. The task text supports up to 200 characters. 7. In Nadlanite, **Contact roles** also lets you choose **Buyer**, **Seller**, or both. Role details are optional; see [seller properties](https://docs.lead-knight.com/en/contacts/seller-property/) for the property workflow. 8. Click **Save**. The list refreshes. A contact saved in the first active stage opens its contact panel; one saved in a later active stage opens the communication-logging flow. ## Duplicate and identity rules Saving is unavailable while duplicate checking is running or an existing match is shown. Click the **Exists:** match to open the existing record instead of creating another. In a team, a restricted match may identify its owner rather than reveal the person's details. A name containing only spaces is not valid. The name limit is 120 characters. An email must be valid when supplied. Changing the workspace's required-details setting is an owner/admin action under **Contact settings** → **Columns** → **Required contact details**; it does not make blank mandatory fields acceptable in this dialog. ## If something goes wrong | Symptom | What to check | What to do | | --- | --- | --- | | **Missing:** appears | Name, required identity details or stage is absent | Complete the listed fields and save again. | | The upcoming-task warning appears | Only task text or only its date is filled | Complete both, or clear both. | | **Save** is disabled | A duplicate check is pending or a match exists | Wait for the result, then open the existing record or correct the entered details. | | A required phone/email error appears after saving | The workspace requirement may have changed | Follow the requirement in the error and supply the missing detail. | | **New contact** is missing | Your role may be viewer | Ask a workspace owner/admin about your role. | ## Related pages - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) - [Import a spreadsheet](https://docs.lead-knight.com/en/contacts/import-contacts/) - [Follow-up tasks](https://docs.lead-knight.com/en/contacts/follow-up-tasks/) - [Edit details and tags](https://docs.lead-knight.com/en/contacts/details-and-tags/) ## Add a contact [Add a contact](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J2/nadlanite-en-6f384ec73533.mp4) 1. To add someone to your CRM, click New contact. 2. Enter their name. 3. Add a phone number or an email. At least one is required. 4. Choose how they found you. 5. Mark whether this is a buyer or a seller. 6. You can also add an upcoming task with a due date. 7. Click Save. 8. The contact is saved, and their record opens with tasks, notes and history. --- # Import contacts from a spreadsheet Prepare a CSV or XLSX file, map its columns and review created, updated, skipped and failed rows without assuming the whole file succeeded. Canonical: https://docs.lead-knight.com/en/contacts/import-contacts/ ## What import does Import creates new contacts and enriches matching existing records. It is not a bulk overwrite: existing names and identity details are retained when already present, missing details can be filled, and tags can be merged. Results are reported per file and per problem row. ## Before you start - Use a workspace owner or admin account; other roles do not see **Import** on **Contacts**. - Prepare a UTF-8 CSV or Excel `.xlsx` file with column headers. Legacy `.xls` is not supported. - Keep the file at or below 2 MiB (2,097,152 bytes), with at most 5,000 data rows, excluding the header. These are Contacts import limits, not the separate audience-import limits. - Give each mapped column a distinct, nonblank header. Repeated nonblank headers are rejected. Keep the sheet to at most 100 columns; parser limits also restrict cell lengths to 4,096 characters for CSV and 500 for XLSX. - Include a name column and at least one phone or email column. New contacts must satisfy your workspace's **Required contact details**; mapping one identity column alone does not override a requirement for both. ## Upload and map the file 1. Open **Contacts** and click **Import**. The **Import contacts** dialog opens. 2. Under **CSV or Excel file**, click **Choose file**, or use **Drop a file here or choose a file**. After the preview finishes, the dialog shows the filename, data-row count and sample values. 3. Review the suggested mappings. Recognized English and Hebrew headers can be mapped automatically, but you must check them against the sample. 4. Map **Name**, **Phone** and **Email** to the correct file columns. **No column** leaves an optional field unmapped. Saving remains disabled without a name column and at least one phone/email column. 5. Map optional **Tags**, **Source**, **Notes** and configured custom contact fields. For tags, notes and custom fields, **Fixed value** applies one value to every row instead of reading a file column. A field cannot use both methods at once. 6. Choose **Default source** for rows that need the fallback source. Choose **Owner** if the new contacts should belong to another eligible teammate. Existing matched contacts keep their owner. 7. In Nadlanite, **Buyer / seller** can add a buyer role, seller role or both to imported contacts. **None** adds neither; import does not remove existing roles. 8. Click **Import contacts**. While work is in progress the button shows **Importing…**. Wait for the result rather than submitting the same file again. 9. Review **Created**, **Updated**, **Skipped (hidden details)**, **Possible duplicates** and **Errors**. Check each listed **Row** before treating the import as complete. ## Fixed values and custom fields A fixed tag list supports up to 20 tags, each up to 40 characters. Fixed notes support up to 4,000 characters; fixed custom values up to 500 characters. Custom values must also fit their configured type, such as number or date. An invalid fixed value blocks submission; correct the highlighted input rather than deleting the entire mapping. The preview lasts 15 minutes. If it expires, select the file again and review the mapping again. A preview is tied to the user and workspace that uploaded it. ## What happens to matches | Row outcome | Meaning | | --- | --- | | **Created** | A new contact was created from a valid row. | | **Updated** | Phone/email matched one accessible contact; import can fill missing values and merge tags without replacing its existing owner. | | **Skipped (hidden details)** | A match exists but its details are not visible to you. It is left unchanged; the result can identify the owner without exposing the record. | | **Possible duplicates** | For example, the phone points to one existing contact and the email to another. The conflicting row is flagged rather than imported as another record. | | **Errors** | These rows failed validation. Other valid rows may already have been imported. | Existing names and phone/email values are not replaced simply because the spreadsheet has different values. Custom fields fill blanks. An identical note already added by the importing user is not added again. To intentionally edit an existing record, use [contact details](https://docs.lead-knight.com/en/contacts/details-and-tags/). ## If something goes wrong | Message or error | Meaning and next step | | --- | --- | | **Only CSV or Excel files can be imported.** | Unsupported file type. Export as CSV or `.xlsx`; changing a filename is not a repair. | | **The file is too large or has too many rows.** | Split the file below the size and row limits, keeping headers in each file. This can correspond to `import_too_large` or HTTP 413. | | **This file can't be imported safely. Choose a different file.** | `import_file_unsafe`: the file failed safety checks; XLSX size/row limits and the upload size guard can also produce this error. Export a clean, smaller CSV/XLSX and choose it again. | | **The CSV file is invalid.** | CSV parsing failed or headers are duplicated. Check quoting and unique headers, then re-export. | | **Could not import contacts. Please try again.** | A general failure, including `invalid_file` for malformed XLSX. Re-export a valid workbook or CSV and select it again. | | **This import has expired. Choose the file again.** | The temporary preview is no longer available. Re-select and remap the file. | | **A selected column is not in the file. Choose the file again.** | Mapping no longer matches the preview. Choose the intended file again. | | **Import is busy. Try again shortly; if previews are full, they expire within 15 minutes.** | `import_busy`: temporary import capacity is full. Wait and retry rather than repeatedly opening more previews. | | **Invalid phone number.**, **Invalid email address.** or **Missing:** | Correct the indicated row and satisfy the workspace identity requirement. Import corrected failed rows rather than assuming every original row failed. | ## Related pages - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) - [Add one contact](https://docs.lead-knight.com/en/contacts/add-contact/) - [Edit details and tags](https://docs.lead-knight.com/en/contacts/details-and-tags/) - [Audiences](https://docs.lead-knight.com/en/audiences/overview/) ## Import contacts from a spreadsheet [Import contacts from a spreadsheet](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J3/nadlanite-en-8f994fdc34b4.mp4) 1. To bring in contacts from a spreadsheet, click Import. 2. Choose a CSV or Excel file. 3. Your columns are matched to contact fields automatically. Change any match from the list. 4. Set a default source for everyone in the file. 5. You can also mark them as buyers or sellers and choose their owner. 6. Click Import contacts. 7. When it finishes, you see how many contacts were created, updated or skipped. --- # Move a contact through the pipeline Change a contact's deal stage from the table, Kanban or contact panel, and record a reason when a deal is lost. Canonical: https://docs.lead-knight.com/en/contacts/move-through-stages/ ## What a stage means A contact's stage describes where its deal stands. Stage labels are customizable, so your workspace may use names different from the examples in a video. The underlying stage meaning stays the same when its label changes. ## Before you start Open **Contacts** and find the record. Moving a contact requires write access to its deal, a non-viewer role and an unfrozen record. If the stage is private, you cannot use the hidden stage as an editable pipeline position. ## Change the stage 1. In **Table**, use the contact's **Stage** selector and choose the destination stage. You can also open the contact panel and change its stage there. 2. Alternatively switch to **Kanban**. On desktop, drag an editable contact card into the destination stage column. Scroll horizontally to reach columns off-screen. Opening the contact panel and using its selector is an alternative to dragging. 3. For a stage with a lost meaning, the **Loss reason** dialog opens instead of immediately completing the move. 4. Choose **Reason** from **Bought elsewhere**, **Not serious**, **No answer** or **Other**. Add an optional **Note** for context. 5. Click **Save**. The move is saved and the list refreshes. **Cancel** dismisses the loss dialog without saving that move. 6. Check the new stage in the list or destination column. Select a next task separately if follow-up is needed; changing a stage is not the same as scheduling a task. ## Reading the board Each Kanban column shows its stage label and contact count. When deal values exist, totals are displayed by currency rather than combining different currencies. A separate **Stage private** column can hold records whose deal stage you cannot see. The stage meanings shown in settings include **In progress**, **Qualified**, **Meeting held**, **Won**, **Lost** and **Not relevant**. Their displayed contact-stage labels may be renamed by your workspace. Do not infer a meaning from color alone. ## If something goes wrong - A card will not drag: check deal access, your role and whether the contact is frozen. Try opening the panel to see available actions. - The loss dialog says **Missing: Reason**: select a reason, then save again. - The card appears absent after moving: clear search and attention filters, and inspect the destination stage. Filters still apply after a move. - A save error appears: the move has not been confirmed; use the displayed error rather than assuming the card's position proves success. - The stages do not match your process: an owner/admin can [customize stages](https://docs.lead-knight.com/en/contacts/customize-stages/); you do not need a second contact record. ## Related pages - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) - [Customize stages](https://docs.lead-knight.com/en/contacts/customize-stages/) - [Follow-up tasks](https://docs.lead-knight.com/en/contacts/follow-up-tasks/) - [Calls and messages](https://docs.lead-knight.com/en/contacts/communication-history/) ## Move a contact through your pipeline [Move a contact through your pipeline](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J4/nadlanite-en-255f1386d8f5.mp4) 1. Each contact has a stage, from New through to Won or Lost. 2. Click the stage to change it. 3. Pick the next stage as the deal moves forward. 4. The contact moves to that stage. Moving someone to Lost asks for a reason. --- # Customize contact stages Rename, reorder and add pipeline stages, set idle thresholds and safely move contacts out of a stage you remove. Canonical: https://docs.lead-knight.com/en/contacts/customize-stages/ ## What this changes Stage settings define the pipeline for the workspace, not just your personal view. You can change labels and order, add open stages and choose when active contacts become idle. Renaming does not change a stage's underlying meaning. ## Before you start You must be a workspace owner or admin. Open **Contacts** and use the gear button labeled **Contact settings**. In a team, ordinary members may have access to privacy settings without permission to manage the pipeline. ## Rename, arrange and add stages 1. Open **Contact settings** and choose **Stages**. Existing rows appear in pipeline order. 2. Edit a stage's name. The **Meaning** column stays fixed and explains the stage's behavior even after renaming. 3. Use **Move up** or **Move down** to change its position. Colors follow position; active stages use shades along the pipeline, while terminal meanings retain their own colors. 4. For an active stage, fill in **Idle days** to set its **Idle after** threshold, or clear the value for no threshold. The allowed range is 1–365 days. Terminal won, lost and not-relevant stages do not offer an idle threshold. 5. Click **+ Add stage** to create another stage. Enter its name; new stages have an in-progress meaning. The UI allows up to 21 total stages. 6. Click **Save stages**. The dialog closes after a successful save and the contact views refresh with the updated configuration. Changing stage order can also change which nonterminal stage is treated as the first active stage for new contacts. Check the order deliberately, not just the colors. ## Remove a stage without stranding contacts 1. Use **Delete** on an eligible stage. Only stages with an **In progress** meaning are deletable in this editor. 2. A **Move contacts to** selector appears for each removed saved stage. 3. Choose an existing retained destination. Lost and not-relevant stages are not offered as migration destinations. 4. Click **Save stages** to submit the removal and destination together. Qualified, meeting-held and terminal stages cannot be removed through this editor, even if you rename them. Every remaining stage needs a nonblank name, and every deleted saved stage needs a destination before saving. ## Other settings beside the pipeline **Columns** manages custom fields displayed in the table and contact details. It also contains **Required contact details**, where owners/admins choose **Phone**, **Email**, **Phone and email** or **Phone or email**, then click **Save required contact details**. That is a separate save from **Save stages**. ## If something goes wrong - **Missing:** appears: fill blank stage names and choose destinations for deleted stages. - A trash button is disabled: that stage's fixed meaning cannot be deleted; renaming it does not change this rule. - **Settings changed. Please try again.** appears: another change made your open configuration stale. Reopen the settings with the latest data and reapply your intended changes. - **Could not save the change** appears: review the error and reopen the latest configuration before retrying; do not assume unsaved rows changed everyone's pipeline. ## Related pages - [Move a contact through the pipeline](https://docs.lead-knight.com/en/contacts/move-through-stages/) - [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) ## Customize contact stages [Customize contact stages](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J11/nadlanite-en-789d4ea36c76.mp4) 1. To fit the stages to how your office works, click the settings gear on Contacts. 2. The Stages tab lists every stage in order. Colors follow position. 3. Click a stage to rename it. Its meaning stays the same. 4. Idle days sets how long a contact can wait before it needs attention. 5. You can also add a stage, or reorder them with the arrows. 6. Click Save stages. 7. The new names show up everywhere, like in each contact’s stage list. --- # Edit contact details and tags Update a contact's name, contact information, source, custom fields and deal details, and enter tags with the correct comma-separated format. Canonical: https://docs.lead-knight.com/en/contacts/details-and-tags/ ## What this does Use a contact's **Details** tab to keep its information current without creating another record. You can update contact information, describe how the person found you, add tags and maintain deal details. Workspace-defined contact fields appear under **Columns**. Most edits here save inline: leaving a text field or choosing an option submits the change. This is different from adding a note or editing a task, which have their own action buttons. ## Before you start - Open **Contacts** in the correct workspace and find the existing person. - You need edit access to the relevant category. Contact information, source, tags and custom contact fields use contact-card access; **Deal value**, **Currency** and **Commission** use deal access. - Viewers cannot edit. A frozen contact cannot be edited, even when you normally have permission. - Keep the workspace's required contact information. Depending on its settings, it can require **Phone**, **Email**, **Phone and email**, or **Phone or email**. Read-only values are not editable buttons. Restricted information may be hidden; being able to open a record does not mean every field is available. ## Update a contact 1. Click the person's name or card in **Contacts**. The contact panel opens and loads the full record. 2. To change **Name**, click the name at the top. Enter the new name and click outside the field, or press Enter. The change is submitted when the field loses focus. Escape cancels this name edit. 3. Choose **Details**. You see the contact's configured fields, source and entry information, contact details, deal fields and **Tags**. 4. Click the current value beside **Phone** or **Email**, enter the correction, then click outside the field. The changed value is submitted automatically; there is no panel-wide **Save** button for these fields. 5. Under **How they found us**, click the source value and select an offered option. The selection saves immediately. Edit **Source details** separately and leave that field to save its text. 6. Under **Columns**, click a custom field's value. Text and number fields save when you leave them. Choice, yes/no and date fields save when you choose a value. The names and available choices depend on your workspace's configuration. 7. Update **Deal value**, **Currency** or **Commission** if needed, using the rules below. Text/number edits save when you leave the field; a currency selection saves when selected. 8. Edit **Tags** using the format below, then click outside the tag editor. The new tag list is submitted. Check for an error in the panel before moving on. **Added through** shows how the record entered the CRM, who added it when available and the date. It is information to review, not an editable source selector. Changing **How they found us** does not edit that entry record. ## Tag format and limits The editor contains one comma-separated list, not a separate Save action for every tag. | What you want | What to enter in **Tags** | | --- | --- | | Two ordinary tags | `priority, newsletter` | | One tag containing a comma | `"North, central"` | | A tag containing quotation marks | `"Asked for ""premium"""` | | A quoted tag followed by another | `"North, central", priority` | | Remove all tags | Clear the field, then click outside it. | - A contact can have at most 20 tags; each tag must be 1–40 characters. - Commas outside quotation marks separate tags. To include a comma inside one tag, enclose the whole tag in double quotes. - Within a quoted tag, write a literal double quote twice: `""`. - The multiline editor also accepts line breaks within quoted tags. A line break is not the separator between tags; use commas between tags. - Unquoted values have surrounding whitespace removed, and empty comma-separated entries are ignored. - Close every quoted tag. After its closing quote, only spaces/tabs, a comma or the end of the list are valid. > **Tip:** Use consistent tag spelling across contacts. A tag is a label on this record; see [Audiences](https://docs.lead-knight.com/en/audiences/overview/) for working with audience lists. ## Field options and validation | Field | Rule | | --- | --- | | **Name** | Required, up to 120 characters; spaces alone are not a name. | | **Phone** | Up to 32 characters in the submitted value; an invalid phone can still be rejected. | | **Email** | Must be a valid email address when supplied, up to 254 characters. | | **Source details** | Up to 200 characters. Clearing it removes that detail. | | Custom contact fields | Text values support up to 500 characters. Date fields must contain real dates. Use the configured options for choice fields. | | **Deal value** | A nonnegative amount. Clearing it removes the amount; the currency selector is disabled without an amount. A new amount uses the existing currency, or ILS if none was set. | | **Commission** | A percentage from 0 to 100. Clearing the override uses the workspace default instead. | Clearing **Phone** or **Email** is allowed only when the remaining information still meets the workspace's identity requirement. Do not remove required information merely to resolve a format error; correct it instead. ### Editing while logging a conversation The communication workflow can offer **Update details**. That separate dialog edits **Name**, **Phone**, **Email** and, when permitted, **Tags**. Unlike the inline fields in **Details**, it requires **Save**; **Cancel** leaves that dialog without saving its changes. The same tag quoting and limits apply. ## If something goes wrong | Symptom | Likely cause | What to do | | --- | --- | --- | | Clicking a value does not open an editor | The field is read-only, your role is viewer, or the contact is frozen | Ask the owner/admin to review the category permission or frozen status. | | **Could not save the change** appears after editing tags | Quoting is malformed, a tag is too long, or there are too many tags | Reopen **Tags**, correct the syntax, keep within 20 tags of 1–40 characters and leave the field again. | | A **Missing:** message names contact information | The change removed a workspace-required phone/email | Restore or correct the required information and submit the edit again. | | An email or phone change is rejected | The entered value is not valid | Correct the address/number rather than creating a duplicate contact. | | **Currency** cannot be changed | There is no **Deal value** | Enter a deal amount first, then select its currency. | | A deal or commission value returns to its previous value | The amount was invalid, negative, or commission exceeded 100% | Enter a nonnegative amount or a percentage within range. | | **Could not load contacts** appears | The panel could not load the full record | Click **Retry** before editing. | ## Related pages - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) - [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) - [Keep notes](https://docs.lead-knight.com/en/contacts/notes/) - [Manage follow-up tasks](https://docs.lead-knight.com/en/contacts/follow-up-tasks/) - [Audiences overview](https://docs.lead-knight.com/en/audiences/overview/) ## Edit contact details and tags [Edit contact details and tags](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J5/nadlanite-en-eb294c6c7a7b.mp4) 1. Click a contact to open their record. 2. Details holds their contact info, source, deal value and tags. 3. Click Tags, type a tag, then click away to save it. 4. Tags help you group and find contacts later. --- # Add and manage contact notes Keep written context on a contact, see who added each note and when, and understand when the Delete action is available. Canonical: https://docs.lead-knight.com/en/contacts/notes/ ## What this does Use **Notes** to keep written context alongside a contact: preferences, background or information a teammate needs before the next conversation. Each saved note shows its author and date. A note is not a scheduled task and does not create a reminder. For something you need to do at a particular time, use [follow-up tasks](https://docs.lead-knight.com/en/contacts/follow-up-tasks/). To record a call or message as a communication, use **Log a call or message**, rather than treating a note as a communication-history entry. ## Before you start - Open **Contacts** in the correct workspace and locate the existing contact. - You need write access to the notes category to add notes or use its available delete actions. Access to contact details and access to notes are separate. - Viewers cannot write notes. Frozen contacts cannot be changed. - Prepare a note containing actual text, up to 4,000 characters. Whitespace alone is not a valid note. ## Add a note 1. Click the contact's name or card. The contact panel loads the record. 2. Choose **Notes**. The tab includes the number of notes; saved notes appear with author, date and text. 3. Click **Add note**. A text area opens in the tab. 4. Type the note. Line breaks can separate the information into readable paragraphs. The editor accepts up to 4,000 characters. 5. Click **Add note** below the text area. The button is unavailable when the draft is empty or a save is in progress. 6. After the save succeeds, the note appears in the list and the input clears. Check the saved text and author/date to confirm you added it to the intended record. > **Important:** Leaving the note field does not save it. Unlike inline fields in **Details**, a note requires **Add note**. Finish that action before closing the panel or opening another contact. ## Review or remove a note Open **Notes** and use the displayed author and date to distinguish entries. The note body preserves line breaks. The contact panel does not offer an edit action for an existing note. For an update that should retain the earlier context, add a new note. If an entry should be removed, use **Delete** when it is available: 1. Find the exact note and check its author and text. 2. Click **Delete** on that note. This action submits the removal directly. 3. After success, the entry disappears from the list. The panel shows **Delete** only when you have notes write access and you are the note's author, a workspace admin or the workspace owner. Being the contact's owner alone is not the same as being a workspace owner or the author of every note. ## Rules to keep in mind - The 4,000-character limit applies to each note, not to the combined history. - Leading and trailing whitespace are trimmed when saving. - Adding or deleting a note is explicit; neither is an inline autosave. - Deletion is not the same as completing a task. Do not remove a useful note merely because the related follow-up is finished. - Shared access can differ by category. You might be able to read a contact while not being allowed to add notes, or see notes without being able to remove another author's entry. ## If something goes wrong | Symptom | Likely cause | What to do | | --- | --- | --- | | **Add note** is not shown | You lack notes write access, your role is viewer, or the contact is frozen | Ask the contact owner or workspace admin to review your access and the contact's status. | | **Add note** is disabled | The draft is blank/whitespace-only or a save is pending | Enter meaningful text, or wait for the pending action to finish. | | **Missing: Notes** appears | The field contains only whitespace | Replace it with actual text before adding the note. | | You cannot type more | The note has reached 4,000 characters | Shorten it, or split distinct information into separate notes. | | A save error appears and the text remains | The save failed; the editor keeps the draft for retry | Read the error, resolve its cause and click **Add note** again. Do not assume the draft was saved. | | **Delete** is missing on another person's note | The panel limits that action by author/admin/owner status as well as write access | Add a correction as a new note, or ask an eligible workspace admin/owner to handle removal. | | A note is missing after switching contacts | It may have remained an unsaved draft, or you opened a different record | Return to the intended contact and check the saved list before adding anything again. | | **Could not load contacts** appears | The record did not load | Click **Retry**. | ## Related pages - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) - [Edit details and tags](https://docs.lead-knight.com/en/contacts/details-and-tags/) - [Manage follow-up tasks](https://docs.lead-knight.com/en/contacts/follow-up-tasks/) ## Add a note to a contact [Add a note to a contact](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J6/nadlanite-en-0af635812366.mp4) 1. Notes keep what you know about this person. 2. Click Add note and write it down. 3. Click Add note again to save it. 4. The note stays on the contact’s record for your team. --- # Manage contact follow-up tasks Add a dated next action, choose reminder channels, request Google Calendar placement and edit, complete or reopen contact tasks. Canonical: https://docs.lead-knight.com/en/contacts/follow-up-tasks/ ## What this does Use **Tasks** to give a contact a concrete next action and a due date/time. Tasks appear above the contact panel's tabs, so you can review the next step without opening **Notes** or **Details**. The earliest-due open task is marked **Upcoming task**. Overdue open tasks have a highlighted due time. Completed tasks are kept under **Completed**, rather than staying in the active list. ## Before you start - Open **Contacts** in the correct workspace and find the existing contact. - You need write access to the tasks category to add, edit, complete, reopen or delete tasks. Reading the contact alone does not grant this. - Viewers cannot change tasks, and frozen contacts cannot be edited. - Prepare task text of up to 200 characters and a valid date and time. Both are required. - For calendar placement, remember that the target is the contact owner's Google Calendar, not necessarily your own. A teammate's request needs that owner's approval. ## Add a follow-up task 1. Click the contact's name or card. The contact panel opens; find **Tasks** above the tabs. 2. Click **Add task**. An inline editor opens with task text, **Due**, reminder choices and **Add to Google Calendar**. 3. Enter a specific next action, such as calling to confirm a decision. Text cannot be empty or whitespace-only and is limited to 200 characters. 4. Set **Due** to the intended date and time. An incomplete or invalid date/time will not save. 5. Under **Reminder:**, choose the available **In-app**, **Email** and/or **WhatsApp** chips. A selected chip shows a checkmark. The last active reminder chip cannot be switched off. 6. Optionally select **Add to Google Calendar**. If you are not the contact owner, this option is unavailable when the owner has no connected calendar. 7. Click **Add**. During saving, the controls are disabled. After success, the new task appears in the list and the text/date inputs clear. If it is the earliest open task, it is marked **Upcoming task**. 8. If you requested a teammate's calendar, check for **Waiting for {owner}'s approval** with the owner's name. A saved CRM task is not proof that its calendar request has been approved. **Cancel** discards the new-task draft and closes its editor. Enter submits the new task when focus is in a non-button control; Escape cancels the draft when no save is pending. ## Choose reminders | Option or message | What it means | | --- | --- | | **In-app** | Use the in-app reminder channel. | | **Email** | Use email reminders when available for this workspace. | | **WhatsApp** | Selectable when WhatsApp reminders are available and your WhatsApp is connected. | | **Email reminders are not available right now.** | The email chip is unavailable; do not rely on email delivery while this message is shown. | | **WhatsApp isn't connected, so these reminders go by email for now.** | A remembered WhatsApp choice is retained, but email is used while WhatsApp is disconnected and email is available. | | **Reminds you as set in your notification settings.** | This task has no explicit channel selection and follows notification settings. | Your changed reminder-chip selection is remembered for the next new task. Editing another task can also update that remembered choice. Older tasks with no explicit channels can follow notification settings instead of showing a fixed selection. When WhatsApp is selected in the saved choice but disconnected, its chip appears off. The saved choice can become active again after connecting. **Connect WhatsApp** takes you to the connections page when that connection can be made. If WhatsApp reminders are unavailable for the workspace, do not assume connecting alone will enable them. ## Google Calendar and owner approval Selecting **Add to Google Calendar** requests a 30-minute event at the task's due time on the contact owner's calendar. - For your own contact, calendar synchronization uses your connected Google Calendar. - For another person's contact, adding a task to their calendar requires approval. If their calendar is not connected, the checkbox is disabled and the panel names the owner whose calendar is missing. - Moving an existing calendar-linked task as a teammate also requests approval. The original due time stays in place until the move is approved; the pending request displays the proposed time. - The contact owner sees the request in their contact panel and chooses **Approve** or **Decline**. An owner must be able to edit the nonfrozen contact to use those decision controls. - Only the contact owner can turn off calendar placement for an already calendar-enabled task. The editor explains this with **Only the contact owner can remove an item from their calendar**. - The calendar checkbox is disabled on a completed task. Calendar status is separate from saving the task: | Status | How to read it | | --- | --- | | **Syncing with Google Calendar** | Calendar synchronization is in progress. | | **On Google Calendar** | The task is on the calendar. | | **Not on Google Calendar** | The task is not currently on the calendar; check the owner's connection. | | **Google sync failed** | The calendar operation failed; the CRM task and calendar placement are not the same result. | | **Waiting for {owner}'s approval** | The owner has not yet decided the requested add or move. | ## Edit, complete, reopen or delete ### Edit a task 1. Click the task text. Its editor opens below the row. 2. Change its text, **Due**, reminder chips or permitted calendar option. 3. Click **Save**. Changed values are submitted and the editor closes after success. Unlike inline contact details, task edits are not saved simply by leaving a field. Enter saves when focus is in a non-button control; Escape closes the editor without saving the draft when no request is pending. ### Mark complete and reopen 1. Click the circle beside an open task. Its accessible action is **Mark completed**, followed by the task text. 2. After success, the task leaves the active list and appears under **Completed**. Its pending due reminder is cancelled. 3. Click **Completed** to expand the saved completed tasks. 4. Click the checked circle beside the task, whose action is **Reopen**. It returns to the active list and its due reminder is armed again using its due time. Reopening does not choose a new date for you. If the old due time is no longer appropriate, open the task editor, change **Due** and click **Save**. ### Delete a task Click the task text, then **Delete** in its editor. The action removes the task from the list and cancels its reminder. Use completion rather than deletion when you want to retain the completed work in **Completed**. ## If something goes wrong | Symptom | Likely cause | What to do | | --- | --- | --- | | **Add task** or completion/edit controls are missing | Tasks are read-only, your role is viewer, or the contact is frozen | Ask the contact owner/admin to review task access and contact status. | | **Missing: Tasks** | Task text is blank or whitespace-only | Enter the action you want to take. | | **Missing: Due** | Date/time is missing, incomplete or invalid | Choose a complete, valid **Due** value and submit again. | | Text cannot grow past 200 characters | The task text limit is reached | Shorten the action; put longer background in **Notes**. | | Saving fails but the editor still contains your text | The request failed and the draft was retained | Read the panel error, resolve it and retry **Add** or **Save**. | | A reminder chip cannot be clicked | The channel is unavailable, or it is the only selected chip | Check the accompanying message; select another available channel before disabling the last one. | | The calendar checkbox is disabled | Owner calendar is disconnected, removal is owner-only, or the task is completed | Follow the explanation in the editor; ask the owner to connect/manage their calendar, or reopen the task when appropriate. | | A teammate's date change is not reflected in the row | A calendar move is awaiting owner approval | Check the proposed time and ask the contact owner to review the request. | | **This request has expired** or **This request was already handled or changed** | The displayed approval request is no longer current | Reopen the contact to review the current task and request before trying again. | | Completed work seems missing | **Completed** is collapsed | Expand **Completed** to find it or reopen it. | ## Related pages - [Contacts overview](https://docs.lead-knight.com/en/contacts/overview/) - [Add a contact with an upcoming task](https://docs.lead-knight.com/en/contacts/add-contact/) - [Keep notes](https://docs.lead-knight.com/en/contacts/notes/) - [Edit details and tags](https://docs.lead-knight.com/en/contacts/details-and-tags/) - [Calendar overview](https://docs.lead-knight.com/en/calendar/overview/) - [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/) ## Add a follow-up task [Add a follow-up task](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J7/nadlanite-en-32f733edcd39.mp4) 1. To plan a follow-up, click Add task. 2. Describe what needs to happen. 3. Set a due date, for example tomorrow morning. 4. Choose how to be reminded: in the app, by email, or on WhatsApp. 5. Click Add. 6. The task appears on the record and in the attention bar when it is due. --- # Log calls and messages and read communication history Record first contact, rate conversations, complete follow-up tasks, and distinguish CRM history from calling or messaging outside the app. Canonical: https://docs.lead-knight.com/en/contacts/communication-history/ ## What this is for Use communication logging to record what happened with a contact, how it went, and what needs to happen next. The **Communications** tab combines logged interactions and past meetings in **History**. Meetings that have not ended or been checked in appear separately under **Meetings**. > **Important:** **Call**, **Send email**, and **Message** open your device's calling app, email app, or WhatsApp. They do not log a conversation or prove that a call connected or a message was sent. Return to the contact to record the outcome. ## Before you start - Open **Contacts** and select the contact to open their details. - You need write access to **Communications**. A read-only, private, or frozen contact can prevent logging or editing. - First-contact logging also updates the contact's progress, so it requires permission to edit the deal. Adding or completing tasks requires task write access too. - Decide whether you actually reached the person. An unanswered attempt is not first contact. ## Record first contact 1. Open the contact's **Communications** tab and click **Log a call or message**. If no first contact has been recorded, the **First contact made** dialog opens. You can also use **First contact made** in the contact header while that button is available. 2. Under **How did you talk?**, select **Call**, **WhatsApp**, **Email**, **SMS**, **In person**, or **Other**. This describes the interaction; it does not send anything through that channel. 3. Under **How did it go?**, choose 1–5 stars. A first-contact rating is required; without it, saving shows **Missing: Rating**. 4. Enter an optional **Summary**, up to 2,000 characters. Record useful context rather than treating this as a message composer. 5. Under **What comes next?**, optionally fill **Tasks** and **Due**. Each task needs both text and a date/time. Use **Add task** for more rows or **Delete** to remove an extra row. Leave both fields blank to create no task. A first-contact save accepts at most 10 tasks, each up to 200 characters. 6. If the contact's details need correcting and you have card edit access, click **Update details**. The quick editor lets you change their name, phone, email and, when permitted, tags. Save those changes to return to logging. 7. Click **Save**. The dialog closes and the interaction appears in **History**, marked **First contact made**, with its channel, author, time, rating and any summary. First contact is recorded. If the contact is still in the first configured stage, this flow moves it to the second configured stage; it does not move a contact that is already further along back to that stage. ## Log a later conversation 1. Open **Communications** and click **Log a call or message**. After first contact exists, the title is **Log communication with {name}**, using the contact's name. 2. Choose the channel, optionally rate the conversation, and fill **Summary** if useful. A later interaction can be saved without a rating. 3. If open tasks are listed under **Complete open tasks**, select only the tasks this conversation actually completed. First-contact task-planning rows are not shown in this later-conversation flow. 4. Click **Save**. The interaction is added to **History**, and selected open tasks are completed. ## Record a call that was not answered The unanswered-call choice is a separate shortcut, not a checkbox inside the ordinary logging dialog. 1. In the contacts table or board, click the contact's **Upcoming task** area. For a contact in the first configured stage, the dialog asks **Did the lead answer?**. 2. Choose **No answer** to save an unanswered call immediately. The dialog closes; the attempt is recorded in history and the unanswered-attempt indicator updates. There is no rating, first-contact outcome, new task or task completion attached to this attempt. 3. If the person did answer, choose **Answered** instead. This opens the logging form, including **First contact made** when first contact has not yet been recorded. Complete and save that form. An unanswered call does not set first contact, advance the stage, change the average rating, or update **Last contact**. A first-stage contact can therefore remain **Awaiting first reply** after repeated attempts. The attempt count remains recorded after a later successful conversation. If the contact is no longer in the first configured stage, this shortcut opens logging directly rather than showing **Did the lead answer?**. Opening **Log a call or message** from the contact drawer also goes directly to logging. Do not rate an unanswered attempt as though it were an answered conversation. ## Read and correct history - **History** is ordered newest first and mixes communication entries with past or checked-in meetings. Upcoming meetings are ordered by their start time under **Meetings**. - Each communication shows its channel, author and time. First contact has a **First contact made** marker; unanswered calls have **No answer**. - For answered interactions, the author or a workspace owner/admin with communication write access can click the stars to change the rating. - Open the entry's **Actions** menu and choose its **Summary** item to edit the summary, then **Save** or **Cancel**. - For a rated, non-first interaction, **Clear rating** removes the rating. **Delete** is available for editable non-first entries. The first-contact entry cannot be deleted or have its required rating cleared from this menu. - Unanswered entries do not offer these answered-conversation editing controls. ## If something goes wrong | What you see | Why it happens | What to do | |---|---|---| | No communication has been logged yet | No visible CRM history exists; using external contact buttons does not create it | Log the actual conversation with **Log a call or message** | | **Missing: Rating** | First contact needs a rating | Choose 1–5 stars and save again | | **Missing: Tasks/Due** | A first-contact task is incomplete or its date/time is invalid | Fill both fields correctly or clear both | | Logging is unavailable or saving is refused | Communication, deal or task permissions may be insufficient, or the contact is frozen | Ask the contact owner to review the relevant access; do not substitute a fake outcome | | No **No answer** option in the drawer | Unanswered logging belongs to the first-stage **Upcoming task** shortcut | Use that shortcut when applicable; the ordinary dialog has no unanswered switch | | No edit or delete menu | The entry is unanswered, is protected first contact, or you lack editing rights | Keep the original record; ask the author or authorized owner/admin about eligible corrections | ## Related pages - [Contacts and CRM overview](https://docs.lead-knight.com/en/contacts/overview/) - [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) - [Move contacts through stages](https://docs.lead-knight.com/en/contacts/move-through-stages/) - [Schedule and document meetings](https://docs.lead-knight.com/en/contacts/meetings/) ## Log a call or message [Log a call or message](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J8/nadlanite-en-6d4030fd8e52.mp4) 1. After a call or message, click Log a call or message. 2. Choose how you talked. 3. Rate how it went. 4. Write a short summary of what you discussed. 5. Click Save. 6. The conversation is now in the contact’s history. --- # Schedule meetings, video calls, and follow-up check-ins Create a contact meeting, request Google Meet and email invitations, understand the contact owner's calendar approval, and record the outcome. Canonical: https://docs.lead-knight.com/en/contacts/meetings/ ## What this is for Schedule a meeting from a contact and keep its time, place, calendar status and outcome together in the CRM. A video meeting can request a Google Meet link and an invitation to the contact's saved email address. Saving a CRM meeting is not proof that Google Calendar has synchronized, a Meet link has been generated, or an invitation has arrived. Check the meeting card's calendar status and join link separately. ## Before you start - Open **Contacts**, select a contact, and open **Communications**. - You need meeting write access. Read-only access, private meeting information or a frozen contact can prevent changes. - Google Calendar actions use the contact owner's calendar, not whichever teammate happens to create the meeting. The owner needs a connected calendar for synchronization. - To invite the contact from the video meeting form, save a valid **Email** on their contact card first. A phone number alone is not an invitation address. - Check the date/time on your device. The meeting form interprets the entered time in your browser's local time zone; meeting cards display dates in the workspace time zone. ## Create a meeting 1. In **Communications**, click **Schedule meeting**. The form opens with **Type** and meeting details. 2. Choose **In person**, **Phone**, or **Video call**. In Nadlanite, **Property visit** is also available. The default for a new meeting is **In person**. 3. Fill **Title**, up to 120 characters. Add **Place** if useful, up to 200 characters; it is optional. 4. Set **Start** and **End**, including both dates and times. The end must be later than the start. 5. Fill any additional meeting fields configured by your workspace. Their labels and available choices depend on the workspace, not on a fixed set in this guide. 6. For **Video call**, review **Create a Google Meet link** and, if an email is saved, **Send an invitation to the contact**. Both are selected by default for a new video meeting. Leave selected only what you intend to request. 7. Click **Save**. The form closes after the CRM record is saved. An upcoming, unchecked meeting appears under **Meetings**; a past or checked-in meeting appears in **History**. Check its calendar status before assuming the calendar-side action succeeded. ## Video calls and invitations - **Create a Google Meet link** requests a conference link through Google Calendar. It does not generate a link independently of calendar synchronization. - **Send an invitation to the contact** appears only when the contact has an email. The invitation uses that saved address; the form does not offer a separate recipient entry box. - Without an email, the UI does not request an invitation. Add the email to the contact and reopen the meeting editor if an invitation is needed. - Meet-link creation and invitation are separate choices, available for **Video call**. Other meeting types do not retain these video options. - Once a Meet URL is available, the card shows **Join**, which opens the link in a new tab. A saved video meeting without **Join** does not yet have an available link. ## Understand the owner's Google Calendar ### When you own the contact Meetings synchronize automatically when your calendar is connected; the meeting form has no per-meeting calendar opt-out. Look for **On Google Calendar**, **Syncing with Google Calendar**, **Not on Google Calendar**, or **Google sync failed** on the card. For an eligible unsynced meeting, open **Actions** and choose **Add to calendar again** when offered. A pending or synchronized meeting does not offer this same retry action. ### When a teammate owns the contact Creating a meeting for someone else's contact can save it in CRM without immediately adding it to their calendar. If their calendar is connected, the system creates an owner-approval request. The card shows **Waiting for {owner}'s approval**, with the owner's name. A change to the time of an already calendar-linked meeting also requires owner approval; the requested time is shown alongside the waiting badge, rather than silently moving their calendar event. The contact owner can review the request and choose **Approve** or **Decline**. Only that owner can decide it. Where offered, **Request adding to {owner}'s calendar** requests calendar addition rather than bypassing approval. If the owner has no connected calendar, a teammate's calendar connection does not replace it. ## Edit or document a meeting 1. Find the card under **Meetings** or **History**, open **Actions**, and choose **Edit**. The **Edit meeting** form opens with the saved details. Change the relevant fields and click **Save**. Calendar approval rules still apply. 2. After the meeting's end time, find it in **History** with **Awaiting check-in**. Select 1–5 stars and optionally enter **Summary**. 3. Click **Check-in** if the meeting happened. A held meeting requires a rating; the saved card shows the outcome and rating. Alternatively choose **We didn't meet**. That outcome saves without a rating, even if stars were selected before clicking it. 4. To correct a saved outcome, use **Actions** → **Edit check-in**. **Tell the assistant more** opens the assistant with a drafted question about the meeting; it does not send that draft automatically. **Delete** in the meeting's **Actions** menu removes the meeting record when your permissions allow it and requests removal of its linked calendar event. This is different from a calendar-addition or time-change request; use it only when the meeting itself should be deleted. ## Nadlanite property visits For **Property visit**, the form adds **Property for visit**. Use the search field and select the relevant property; choices include the address, city when available and seller name. The property link is optional. The server rejects linking a seller's own contact as the visitor to their own property. Record the viewing on the visiting contact instead. ## If something goes wrong | What you see | Why it happens | What to do | |---|---|---| | **Missing:** | Title, start or end is missing or a date/time is invalid | Complete **Title**, **Start** and **End** | | **End time must be after the start time** | End is equal to or before start | Correct the date and time, including the end date for an overnight meeting | | No invitation checkbox | The contact has no saved email, or the type is not **Video call** | Save the contact's **Email** and choose **Video call** | | No **Join** after saving | A Meet URL is not available yet | Check the owner's connection, calendar status and any waiting approval; do not assume a link was created | | **Not on Google Calendar** or **Google Calendar is not connected** | The required owner's calendar is unavailable or the event cannot be synchronized there | Ask that owner to connect or review their calendar, then use the offered retry/request action | | **Waiting for {owner}'s approval** | A teammate requested addition or a time change | Ask the contact owner to review the request; do not create duplicate meetings to bypass it | | **Google sync failed** | The calendar-side action failed although CRM may have saved | Review the connection and retry through **Actions** when offered | | Check-in refuses a rating-free held meeting | A held meeting needs 1–5 stars | Choose stars and **Check-in**, or use **We didn't meet** only if it did not happen | | Meeting controls are absent or disabled | You lack meeting write access or the contact is frozen | Ask the contact owner to review access | ## Related pages - [Contacts and CRM overview](https://docs.lead-knight.com/en/contacts/overview/) - [Communication history](https://docs.lead-knight.com/en/contacts/communication-history/) - [Calendar overview](https://docs.lead-knight.com/en/calendar/overview/) - [Account settings](https://docs.lead-knight.com/en/account/overview/) --- # Add and manage a seller's property Enable the seller role, save property facts and prices, understand the draft publishing prompt, and optionally prepare property details for Sites. Canonical: https://docs.lead-knight.com/en/contacts/seller-property/ ## What this is for In Nadlanite, a seller contact can hold multiple property records. Keep listing facts, asking-price history, appraisal, exclusivity, relevant buyers and viewing history with the seller. > **Important:** Saving a property in CRM is not permission to publish social posts. Where sharing allows a linked Properties draft, the property can be added there as a draft and offer a publishing prompt. Choosing **Publish now** opens the next publishing setup; it does not itself post the property. ## Before you start - Use a Nadlanite real-estate workspace. General-purpose workspaces do not show buyer/seller controls. - Open **Contacts** and select the seller's contact. - You need contact-card edit access to change the **Seller** role, and listing write access to add or edit listing details. **Appraisal value** and **Exclusive** are private listing facts with separate permissions. - Have the property's address ready. Adding a new property from this seller editor requires **Property address**. Other role details collected while initially adding a contact are a different flow. - Sites controls are optional. If you do not see **Sites** in the menu, it is not enabled for your workspace yet. ## Enable the seller role and add a property 1. In the contact header, click **Seller** if it is not already selected. The selected role is marked, and the **Seller** tab becomes available. A contact can be both **Buyer** and **Seller**. 2. Open the **Seller** tab. Existing properties appear as selectable property cards. Click **Another property** to open a new property draft. 3. Enter **Property address**, up to 200 characters. Click **Save property** to create the record. For a new draft, the address editor is open first; other property rows become available for editing as you work with the record. 4. If the **Property saved** prompt appears, read the explanation: the property was also added to the Properties page as a draft. Choose **Keep as draft** to close the prompt without starting publication, or **Publish now** to open publishing setup for that linked draft. 5. Select the property's card again if necessary. Click the displayed value or dash beside the field you want to change. The row becomes editable; change it and click **Save property**. Repeat for other fields. **Cancel** discards the current unsaved edit rather than deleting the property. 6. When the property has a linked draft, **Open in Properties** opens its property campaign. Review and finish the publishing flow there only if you actually intend to publish. A private listing does not create a team-visible Properties draft. In that case the property can remain CRM-only, with no publishing prompt or linked-draft button. Do not treat the absence of a prompt as a failed property save; check the seller's property cards. ## Fill the listing fields | Field | How to use it | |---|---| | **Property address**, **City** | Store the address and optional city; city allows up to 100 characters | | **Deal type** | Choose **Sale** or **Rent** | | **Property type** | Choose **Apartment**, **Garden apartment**, **Penthouse**, **Duplex**, **House**, **Plot**, or **Commercial**, or leave it unset | | **Rooms** | Enter 0–50 in half-room steps, such as 3 or 3.5 | | **Bathrooms** | Enter a whole number from 0–20 | | **Area (sqm)** | Enter a whole number from 1–10,000, or leave it blank | | **Floor** | Enter a whole number from -5–200, or leave it blank | | **Property features** | Select applicable **Parking**, **Elevator**, **Safe room**, **Balcony**, **Storage**, and **Accessible** | | **Additional features** | Type a feature and press Enter to add it as a chip; use its remove control to discard a chip before saving | Save each edited row explicitly with **Save property** before moving on. The seller editor is not a single auto-saving property form. ## Prices and exclusivity 1. Click the value beside **Asking price**, enter a nonnegative amount and choose **Currency** if the selector is available. Click **Save property**. A saved asking-price change appears in **Price history**, including the amount, date and person who changed it. 2. After the property has price history, currency is locked; the selector is no longer offered. An existing asking price cannot be removed by simply clearing its input. A reduction between the latest two prices can show a **Price drop** indicator. 3. If permitted, edit **Appraisal value** separately. This is a private fact, not the public asking price; enter a nonnegative amount and click **Save property**. 4. To record exclusivity, open **Exclusive**, select the checkbox and set **Exclusivity ends**. Save the change. An end date is required when exclusivity is active; turning exclusivity off clears that date. **Exclusivity ending** can appear when an active exclusivity period ends within 14 days. If you can edit listing facts but not appraisal or exclusivity, that can be intentional sharing configuration. Listing access and private listing-fact access are distinct. ## Optional property details for Sites When Sites is enabled and a property is saved, **Property on sites** adds website-specific controls. These are separate from the social-post publishing prompt. 1. In **Property photos and videos**, click **Upload photos or videos**. Add images or MP4 videos, up to 256 MB per video, with at most 40 media items total. Uploaded items are not attached to the property until you save the site details. 2. Use the media arrows, **Move earlier** and **Move later**, to set the order, or **Remove** to remove an item from this property's media selection. The first photo is the cover; videos play before photos on the listing page. 3. Review **Show on sites**. A hidden property is excluded from all sites, including teammates' sites. This is site visibility, not a social-post publication grant. 4. Set **Address shown to visitors** to **Site default**, **Full address**, **Street and city (no house number)**, or **Neighborhood and city**. Review **Show price**, fill **Neighborhood** if needed, and add **Property description**. Neighborhood allows up to 120 characters and description up to 2,000. 5. Click **Save site details**. **Site changes submitted** confirms submission. These saved facts and media can update how the property appears on existing sites. **Cancel** restores the saved site details. 6. If you want a separate landing page, click **Create landing page**. This opens Sites with this property selected; creating and publishing that site is a separate workflow. Archived properties are not shown on sites and their site controls are disabled. Saving CRM facts or clicking **Create landing page** does not automatically publish a new website; review site visibility carefully if your property already feeds a published site. ## Buyers, visits and removing records - **Relevant buyers** shows matching buyers with the budget and owner information you are allowed to see. Some matches are privacy-limited cards rather than links to a full contact. - **Property visits** lists visits, dates and recorded outcomes. With access, clicking a visit can open the visiting contact. Use that contact's meeting flow to schedule a **Property visit** and link the property. - Each property has its own **Delete** action when listing write access allows it. Select the correct property before using it; deleting a property is not the same as cancelling an unsaved edit. - You cannot turn off **Seller** while the contact has active properties. The message is **Cannot unset seller while there are active properties**. Review the actual property records rather than deleting them merely to change a role label. ## If something goes wrong | What you see | Why it happens | What to do | |---|---|---| | No **Seller** control or tab | The workspace is not real-estate, the role is not selected, or access is restricted | Check the workspace and role; ask the contact owner about permissions | | **Missing:** on save | A new property's address is blank, a price is invalid, or exclusivity has no end date | Complete the address, correct nonnegative amounts and set **Exclusivity ends** when required | | **Could not save the change** | A value may fail the property's validation or you may lack permission | Check the field limits and your listing/private-fact access | | No publishing prompt | A private listing can remain CRM-only without a linked Properties draft | Confirm the property card exists; review sharing with the owner if a team-visible draft is intended | | No currency selector | Saved asking-price history locks the currency | Keep the existing currency rather than reinterpreting historical amounts | | Media upload fails | The file type, video size or total media count is not supported | Use images or MP4 up to 256 MB each and no more than 40 items, then save site details | | Website media or text does not reflect the edit | Uploads and site edits require an explicit save | Click **Save site details** and look for **Site changes submitted** | | A property is absent from a site | It may be hidden or archived | Review **Show on sites**, archived status and the site's own setup | ## Related pages - [Contacts and CRM overview](https://docs.lead-knight.com/en/contacts/overview/) - [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) - [Meetings and property visits](https://docs.lead-knight.com/en/contacts/meetings/) - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Sites overview](https://docs.lead-knight.com/en/sites/overview/) - [Create a site](https://docs.lead-knight.com/en/sites/create-site/) ## Add a seller’s property [Add a seller’s property](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/J9/nadlanite-en-2d8e79a1d365.mp4) 1. To add a property a seller wants to list, open their contact. 2. Mark them as a seller. 3. A Seller tab appears. Open it. 4. Click Another property. 5. Enter the address, 6. then the city, rooms and asking price. Add more details any time. 7. Click Save property. 8. The property is saved on the seller’s record, ready for a campaign. --- # Audiences Organize people into saved audiences, add or import members, and understand sharing, WhatsApp sources, and the difference between recipients and ad targeting. Canonical: https://docs.lead-knight.com/en/audiences/overview/ ## What an audience is for An audience is a saved group of people. Use it to organize a list without making every person a CRM contact, select recipients in a WhatsApp campaign, or collect leads from an ad into a chosen group. The same person can belong to more than one audience. An **Audience member** and a **Contact** are different person types. Adding a new person by hand, through an audience import, or through a WhatsApp audience source does not by itself promote that person to Contacts. An existing contact can also belong to an audience without becoming a separate duplicate contact. > **Important:** A saved audience is not the same as a paid-ad platform's targeting settings. It is also not proof that its members consented to receive messages. ## Choose a guide | What you want to do | Guide | |---|---| | Create a named audience, choose its language, rename it, merge lists, or delete the audience | [Create and manage an audience](https://docs.lead-knight.com/en/audiences/create-audience/) | | Add a person, link a matching contact, import CSV or XLSX, or move and remove members | [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/) | | Understand preferences, activity, notes, insights, WhatsApp sync, recipient selection, and ad-lead routing | [Use audiences](https://docs.lead-knight.com/en/audiences/use-audiences/) | | Manage a person's CRM record rather than an audience membership | [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) | ## Find and open an audience 1. Open **Audiences**. The list is at `/audiences`. 2. Use **Search audiences** to find a list by name. **Clear search** removes the search text. 3. Review **Name**, **People**, **Source**, **Language**, and **Last send**. Sources can be **Hand-built**, **WhatsApp group**, **WhatsApp label**, or **Phone contacts**. A missing language or last-send value appears as a dash. 4. Click an audience name. Its detail page opens at `/audiences/<id>`. The header shows its people count, **Owner**, and an access badge: **Yours**, **Shared with you**, or **Team**. A synced audience also shows its source and last-sync time. 5. Use **Audiences** above the header to return to the list. On a phone, the list uses audience cards rather than a wide table. Within a detail page, **Actions** contains management commands; larger screens also show **Add person** and **Import** directly. ## The five detail tabs All five tabs are inside the same `/audiences/<id>` page; they are not separate audience URLs. | Tab | What you can do there | |---|---| | **People** | Search members, filter by email, email agreement, tag, or an audience field; open an accessible person's record; select members for actions. | | **History** | Review membership changes and other recorded events, plus **Growth over the last 12 weeks** with joined, left, and unsubscribed totals. | | **Preferences** | Set language, preferred channel, sending hours and days, assistant writing guidance, email-click promotion, audience fields, and permitted sharing. | | **Notes** | Read audience-level notes; with management access, add or delete notes. These are not a person's individual CRM notes. | | **Insights** | Review recorded sends and their recipient, accepted, clicked, and unsubscribed counts. Email sends can also show **Top clicked links**. | See [Use audiences](https://docs.lead-knight.com/en/audiences/use-audiences/) for the controls and empty states in these tabs. ## Who can view or change an audience Audience visibility depends on ownership, explicit sharing, and whether the audience owner's seat is paid by the workspace. Workspace-paid owners' audiences are visible to the workspace; a self-paid owner's audience is not automatically visible to everyone. - A viewer role is read-only: it cannot create audiences or manage their contents. - A non-viewer can manage an audience they own or one shared with them. - For workspace-visible audiences, workspace owners, admins, and members can manage content and preferences. - Deleting an audience, managing its shares, and merging it require stronger rights: the audience owner, or a workspace owner/admin for a workspace-paid audience. Sharing alone does not grant those rights. Shared audiences are not selectable for merging in the list. - Access to an audience does not reveal every member's private CRM details. **Private contact** or limited, non-clickable details can appear when the underlying contact is not shared with you. See [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) for workspace roles. If a command is missing, check your role and the audience's access badge before trying another path. ## Pick the right action - **New audience** creates an empty, named audience. It does not send anything. - **Import** on the audience list creates a new audience from a file. **Import** inside an audience adds to that audience. - **Remove from audience** removes selected memberships only; the people remain in their other audiences and, if applicable, Contacts. - **Delete person** is different: after confirmation, it deletes eligible audience-tier people and removes them from all audiences. Contacts cannot be deleted with this command. - **Delete audience** deletes the list, not its people from Contacts or other audiences. - **Promote to contact** changes an eligible audience member into a CRM contact; audience membership is not the same as promotion. ## If something goes wrong - **No audiences yet. Import a file or keep WhatsApp groups as audiences.** means there are no audiences visible to you. Create one or use a supported population method; an empty list is not a send failure. - **No matching audiences.** means the search has no matches. Use **Clear search** before creating a replacement list. - **Could not load audiences.** has a **Retry** action. A loading failure is not evidence that an audience was deleted. - **You can't change this audience.** means the requested operation is not permitted with your current access. Ask the audience owner or workspace administrator for the appropriate access. - A synced audience with no people yet may still be waiting for WhatsApp sync. Its header's last-sync information helps distinguish that from a hand-built empty list. ## Related pages - [Create and manage an audience](https://docs.lead-knight.com/en/audiences/create-audience/) - [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/) - [Use audiences](https://docs.lead-knight.com/en/audiences/use-audiences/) - [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/) - [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) ## Create an audience [Create an audience](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/K1/nadlanite-en-cb107e791f8b.mp4) 1. An audience is a list of people you want to reach together. Click New audience. 2. Give it a name. 3. Choose the language you’ll write to them in. 4. Click Create audience. 5. The audience opens, ready for people. ## Add people to an audience [Add people to an audience](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/K2/nadlanite-en-2075a22e3c01.mp4) 1. To add someone, click Add person. 2. Enter their name, and an email or phone number. 3. Click Add person. 4. They now appear in the audience. 5. To add many people at once, use Import with a CSV or Excel file. --- # Create and manage an audience Create an audience, choose or change its language, rename it, manage sharing, merge eligible audiences, and delete a list without deleting its people. Canonical: https://docs.lead-knight.com/en/audiences/create-audience/ ## What this guide is for Create a named audience before adding people, or maintain an audience that already exists. Creating, renaming, or changing the language does not send a message or launch an ad. ## Before you start - Open the workspace where the audience should live. A viewer role cannot create or manage audiences. - Choose a useful name, such as the list's purpose or source. Audience names are required and can contain up to 200 characters; spaces alone do not count as a name. - Decide whether to set **Language** to **Hebrew**, **English**, or leave it **Not set**. This is an audience preference, not a translation of every member's record or a change to your app language. - To change an existing audience, you need management access. An audience you own or one shared with you is manageable by a non-viewer. Workspace owners, admins, and members can manage workspace-visible audiences. ## Create an empty audience 1. Open **Audiences** at `/audiences`. You see the audience list or its empty state. 2. Click **New audience**. A dialog opens with **Name** and **Language**. 3. Enter **Name**. The **Create audience** button remains unavailable while the name is empty or contains only spaces. 4. Choose **Language**: **Hebrew**, **English**, or **Not set**. Leaving it unset is allowed. 5. Click **Create audience**. While the request is running, the button shows **Creating…** and the form cannot be edited. 6. After success, the dialog closes and the new audience's detail page opens at `/audiences/<id>`. Its name appears in the header; **People** is the initial tab. 7. Continue with **Add person** or **Import**, either directly on larger screens or through **Actions**. Follow [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/) for those flows. Click **Cancel** before submitting if you do not want to create the audience. A successful creation does not automatically populate the list. ## Rename an audience 1. Open its detail page from **Audiences**. 2. Click the audience name in the header, or choose **Actions** → **Rename**. The name becomes an editable **Name** field. 3. Enter the new name, up to 200 characters. **Save** is unavailable for an empty or spaces-only name. 4. Click **Save**. After a successful request, the editor closes and the header shows the new name. **Cancel** leaves the existing name unchanged. Renaming changes the list's name, not its membership. If the name is not clickable and **Rename** is absent, check your management rights rather than creating another audience as a workaround. ## Change the language and other preferences 1. Open the audience and select **Preferences**. 2. Change **Language** to **Hebrew**, **English**, or **Not set**. 3. Review the remaining settings before saving: **Preferred channel**, **Only send during these hours**, **Sending days**, **How the assistant should write to them**, and **Topics they care about**. 4. Click **Save** in the preferences form. The saved settings belong to this audience. Language is optional. For the rules on sending hours, fields, and the email-click promotion switch, see [Use audiences](https://docs.lead-knight.com/en/audiences/use-audiences/). These settings do not themselves start a send. ## Share an audience Sharing management is available to the audience owner, or to a workspace owner/admin for a workspace-paid audience. It is not granted merely because the audience was shared with you. 1. Open **Preferences** and find **Shared with**. If the section is not shown, your current access does not expose share management. 2. Select the people in the candidate list who should have an explicit share, or clear a selected person to remove their explicit share. 3. Click **Save** in that section. The explicit sharing list is updated. Up to 100 users can be selected. The screen states **Shares never expire. Remove someone to stop sharing.** Removing an explicit share does not remove any separate access the person already has through workspace visibility or ownership. Sharing the audience does not grant unrestricted access to its members' private CRM records. ## Merge existing audiences Merge when several lists should become one, not merely when one person belongs to several useful groups. Merging moves people, notes, and shares from the source audiences into the audience you keep. 1. Return to **Audiences**. 2. Select the checkboxes for at least two and at most 21 eligible audiences, including the audience to keep. Shared audiences are not selectable for merging. Workspace-visible audiences require workspace owner/admin rights for this action; an audience owner can select their own audience. 3. Click **Merge audiences**. The dialog shows **Audience to keep**. 4. Select the surviving audience carefully. That is the audience that opens after the merge. 5. Optionally enter **New name (optional)**, up to 200 characters. Leave it empty to keep the survivor's existing name. 6. Click **Merge audiences**. While saving, the button shows **Merging…**. On success, the survivor's detail page opens. This is a consolidation operation, not a copy. If you want to retain both audiences separately, use the member-level **Copy to audience…** action instead; see [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/). ## Delete an audience without deleting its people > **Important:** **Delete audience** removes the audience. It is not **Delete person**, which removes selected people from all audiences. 1. Open the audience you intend to remove and verify its name and source. 2. Choose **Actions** → **Delete audience**. This command requires the audience owner's rights, or workspace owner/admin rights for a workspace-paid audience. 3. Read the confirmation: **Delete this audience? The people stay in your contacts and other audiences.** 4. Click **Confirm** to delete the audience, or **Cancel** to keep it. 5. After success, you return to `/audiences`. Deleting a WhatsApp-sourced audience also disconnects its retained source from that audience. It does not turn a WhatsApp label into a source of CRM contacts. If the goal is only to remove a few people, use **Remove from audience** instead. ## If something goes wrong | Symptom | What to check and do | |---|---| | **New audience** is missing | Check the selected workspace and your role. Viewers have read-only access. | | **Enter an audience name.** appears | Enter at least one non-space character in **Name**. | | The creation or save request shows an error | Read the displayed error; the dialog stays open. Correct the problem before submitting again. Do not assume an audience was created just because the button was clicked. | | **You can't change this audience.** appears | Your current access does not authorize the operation. Check ownership, sharing, and workspace role. Ordinary management and deletion are different permissions. | | An audience checkbox cannot be selected for a merge | Shared audiences cannot be merged by you; a workspace-visible audience requires owner/admin rights. | | **Select up to 21 audiences to merge.** appears | Reduce the selection to at most 21 audiences, including the survivor. | | Preferences will not save after changing language | Check the rest of the form: sending hours must differ and at least one sending day must remain selected. | | The audience loads, but some people show **Private contact** | Audience access does not override CRM privacy. Ask for access to the underlying contact if needed. | ## Related pages - [Audiences overview](https://docs.lead-knight.com/en/audiences/overview/) - [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/) - [Use audiences](https://docs.lead-knight.com/en/audiences/use-audiences/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) ## Create an audience [Create an audience](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/K1/nadlanite-en-cb107e791f8b.mp4) 1. An audience is a list of people you want to reach together. Click New audience. 2. Give it a name. 3. Choose the language you’ll write to them in. 4. Click Create audience. 5. The audience opens, ready for people. --- # Add and manage people in an audience Add people manually, confirm matching contacts, import CSV or XLSX with column mapping, and choose safely between copying, moving, removing, and deleting people. Canonical: https://docs.lead-knight.com/en/audiences/add-people/ ## What this guide is for Populate an audience one person at a time or from a file, then maintain its memberships. New people added through these audience flows are audience members, not automatically CRM contacts. Existing matching contacts can belong to the audience without becoming duplicates. ## Before you start - Open **Audiences** and the audience you want to populate. You need management access; viewer roles cannot add or import people. - Check the header's audience name before changing its membership. On a phone, open **Actions** for **Add person** or **Import**; larger screens also show these buttons directly. - For a manual addition, prepare a name and an email address or phone number. For an import, at least one file column must be mapped to email or phone. - Use only information you are entitled to store and use. Importing a phone number or email address does not itself establish messaging consent. ## Add one person manually 1. Choose **Add person**. A dialog explains: **Enter a name and an email address or phone number.** 2. Fill **Name**, up to 120 characters in this form. 3. Fill **Email**, **Phone**, or both. A name without either identity field cannot be submitted. Enter a valid email address and a valid phone number; including the international country code helps avoid ambiguity. 4. Click **Add person**. The service checks existing identities before creating a new person. 5. If a visible person is matched by phone under a different name, the dialog can ask **This phone number belongs to {name}. Add this existing contact?** Verify that it really is the same person, then click **Add existing contact**. **Cancel** returns to the input form so you can correct it. 6. After success, the dialog closes and the audience's people data refreshes. Find the person in **People** to confirm the membership. The matching prompt is not shown for every existing identity. An email match, or a matching name, can be linked without that extra prompt. Linking an existing contact does not transfer ownership of the contact or grant access to private information. ## Prepare a CSV or XLSX file The file picker accepts `.csv` and `.xlsx`; old `.xls` files are not accepted. The first row must contain unique, non-empty column headers, each at most 200 characters long. Keep phone values as text in your spreadsheet so leading zeroes and country codes are not lost before uploading. | Limit | What it means | |---|---| | CSV: up to 100 MB | The upload limit is 100 × 1,024 × 1,024 bytes. The audience CSV import does not use Excel's 5,000-data-row cap. | | XLSX: up to 2 MB | The upload limit is 2 × 1,024 × 1,024 bytes. The workbook must also pass the Excel safety checks. | | XLSX: up to 5,000 data rows plus a header | Oversized or unsafe workbooks are rejected rather than silently importing only the first 5,000 people. | | XLSX: up to 100 columns and 500 characters per cell | Workbook structure and expanded content also have safety limits; a small file can still be rejected. | | Up to 40 audience fields | This is the destination audience's total field limit, not 40 extra fields for every upload. | | Audience-field labels: 1–100 characters | Kept fields need non-empty labels. | For large or complex Excel files, save the relevant sheet as CSV. Keep only the columns you need. More than 40 automatically proposed extra audience fields can cause the preview to be rejected before the mapping screen; reduce the file's columns in that case. ## Import into this audience 1. Inside the audience, click **Import**. The **Import people** dialog opens and displays its file limits. 2. Under **Choose a CSV or Excel file**, select the file. **Reading file…** appears while the upload is read. 3. When preview succeeds, inspect **Preview (first 5 rows)**. This is a sample, not proof that every row in the file is valid. 4. Review the suggested column mappings for **Name**, **Email**, **Phone**, and **Tags**. Choose the corresponding file header in each dropdown, or **Don't import** for an unused identity field. You must map at least **Email** or **Phone**. 5. Review **New audience fields**. For each extra column, keep its checkbox selected to retain it as an audience-specific field, edit **Field label** if needed, or use **Don't import** to drop it. Columns already mapped to identity fields or automatically matched CRM fields do not also appear as new audience fields. 6. Check that kept field labels are non-empty and that the final field set fits within 40 fields. Existing CRM custom fields whose labels match a header can be recognized automatically; the dialog does not provide a separate manual CRM-field mapping editor. 7. Click **Start import**. It remains unavailable until the mapping is valid. The dialog changes to **Importing… {processed} rows** once the request starts. 8. Wait for the result. You may use **Close** after the import starts: **You may close this window. The import will continue.** Closing the window does not cancel the background import. 9. On completion, review **Import finished** and the added, updated, and skipped counts. The dialog can display up to five sampled row errors. Click **Done** and inspect **People**. To create a new audience from a file instead, use **Import** on the main **Audiences** list. The same mapping dialog also includes **New audience name**, initially based on the filename. Set that name before **Start import**; successful completion opens the resulting audience. The detail-page import does not ask for a new name because its target is already selected. ## Understand the import result - Email and phone identities are normalized and matched to existing people. Import does not deliberately create a second CRM contact just because the person appears in another audience. - A row with neither a usable email nor a usable phone is skipped. If one identity is invalid but the other is usable, the usable identity can still be imported. - Repeated identities can be skipped. A skipped count is not exclusively a count of errors; not every skipped duplicate receives a row-error sample. - Existing non-empty CRM names, tags, and custom values are not indiscriminately overwritten. Where permitted, the importer can fill missing values; imported audience-specific values belong to that membership. - A new person is stored as an **Audience member**. Use **Promote to contact** when CRM promotion is intended. - A failed import can have already committed earlier rows. Check the counts and current membership before uploading again; failure does not mean the entire import was rolled back. - An unstarted preview expires after 24 hours. Choose the file again if a preview has expired. For tags, separate values with commas, semicolons, or `|`. The importer keeps at most 20 distinct tags per row, with each tag limited to 40 characters. Imported names are limited to 120 characters, and audience-field values to 2,000 characters; do not use this flow to preserve longer text verbatim. ## Find and select people 1. Open **People**. Use **Search people** and, as needed, **Has email**, **Agreed to email**, **Tag**, or **Field** with **Value**. Phone layouts place filters in a filter sheet. 2. Clear restrictive filters if the expected person is missing. **No people match these filters.** does not necessarily mean the audience is empty. 3. Select the checkboxes next to the people to change. **Select all loaded people** selects the currently loaded rows, not every matching person on the server. 4. Use **Load more** to fetch more rows when available. Rows load in batches of 50; bulk selection is limited to 5,000 people. Changing the search or filters clears the selection. 5. Open **Actions** for the selected people. A clickable person's name opens the accessible record. **Private contact** and non-clickable limited details reflect privacy restrictions, not a broken link. ## Choose the correct people action | Action | Result and next step | |---|---| | **Copy to audience…** | Choose a manageable destination in **Choose an audience**, then **Confirm**. The original membership remains. | | **Move to audience…** | Choose the destination, then **Confirm**. The selected people leave this audience and join the destination. | | **New audience from selection** | Enter **Name**, choose **Move** or **Copy**, then **Confirm**. The new audience opens; the chosen mode determines whether the original membership remains. | | **Remove from audience** | Removes only the selected memberships from this audience. It does not globally delete the people or remove other memberships. | | **Promote to contact** | Promotes eligible, visible audience-tier people to CRM contacts. This is not required merely to keep someone in an audience. | | **Don't email** | Applies email suppression to eligible selected people with an email address. It does not remove audience membership. | | **Allow email again** | Offered for manually suppressed email addresses. It is not a way to override every suppression reason or create consent. | | **Delete person** | Opens a global-deletion confirmation. This is not a synonym for removing a membership. | For **Delete person**, read **Delete the selected people? They will be removed from all audiences.** before **Confirm**. It is available only when the selection contains eligible audience-tier people rather than contacts or hidden members; the server also enforces person access and frozen-record restrictions. Contacts must be handled from Contacts, not deleted through this command. ## If something goes wrong | Symptom | Cause or recovery | |---|---| | **File too large** | Reduce the file or use CSV for a list that exceeds Excel's limits. Renaming an XLSX file to CSV is not conversion. | | **Only CSV and Excel files** | Select `.csv` or `.xlsx`; save `.xls` in one of those formats first. | | **This Excel file is too big or can't be read. Save it as CSV and try again.** | Size, row, column, cell, workbook safety, or parsing constraints can reject Excel. Export a simpler CSV and choose it again. | | Preview fails before mapping | Check unique non-empty headers, readable CSV/XLSX content, and the number of extra fields. Remove unnecessary columns and use **Choose another file** if the mapping screen is already open. | | **Map an email or phone column** | Select a header for **Email** or **Phone**. Mapping **Name** alone is insufficient. | | **Check the field labels and selected columns.** | Check kept labels and the 40-field limit. Existing destination fields count toward that total. | | **Could not refresh import progress.** | Use **Retry** in the dialog. A progress-refresh error does not itself mean the background import failed; do not immediately start another upload. | | **The import failed.** | Read the counts and sampled **Row {row}: {reason}** messages. Correct unusable identities or file content; inspect partial results before retrying. | | **Delete person** is disabled | The selection includes a contact or hidden person. Use **Remove from audience** if only membership should change; manage contact deletion in Contacts. | | **This person is no longer available.** or a frozen-contact message appears | The record or your access changed, or the owner's departure is unresolved. Refresh the view; ask the owner/admin to resolve the underlying access or hold. | ## Related pages - [Audiences overview](https://docs.lead-knight.com/en/audiences/overview/) - [Create and manage an audience](https://docs.lead-knight.com/en/audiences/create-audience/) - [Use audiences](https://docs.lead-knight.com/en/audiences/use-audiences/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) - [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) ## Add people to an audience [Add people to an audience](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/K2/nadlanite-en-2075a22e3c01.mp4) 1. To add someone, click Add person. 2. Enter their name, and an email or phone number. 3. Click Add person. 4. They now appear in the audience. 5. To add many people at once, use Import with a CSV or Excel file. --- # Use audiences, preferences, and connected sources Understand audience tabs, WhatsApp-synced people and recipients, and paid-ad lead routing without confusing a saved list with platform targeting. Canonical: https://docs.lead-knight.com/en/audiences/use-audiences/ ## Three meanings to keep separate | Term | What it controls | |---|---| | A saved audience in **Audiences** | Membership of a named group of people, its preferences, notes, and recorded activity. | | **Audiences** in a WhatsApp recipient picker | Which saved groups contribute people to that send's recipients. Selecting a group is not sending to a WhatsApp group chat. | | **Audience** in the paid-ad editor | The advertising platform's targeting: who may see an ad. It is not selection of a saved CRM audience. | A fourth, separate control, **Where leads go**, chooses the saved audience that receives an ad's submitted leads. It controls inbound organization, not who sees the ad. ## Navigate an audience's detail page Open **Audiences**, then click a name. The detail route is `/audiences/<id>`. **People**, **History**, **Preferences**, **Notes**, and **Insights** are tabs on that page, not separate routes. The header shows the owner, access badge, people count, and source/sync information when available. Use [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/) for **People**, including filters, selection, promotion, and removal. Use [Create and manage an audience](https://docs.lead-knight.com/en/audiences/create-audience/) for naming, sharing, merging, and deletion. ## Preferences describe the audience A non-viewer with management access can edit the main **Preferences** form. Review the settings and click its **Save** button; audience fields and sharing have their own save controls. | Setting | Available choices and rules | |---|---| | **Language** | **Not set**, **Hebrew**, or **English**. This is the audience's language preference, not a command to translate all existing information. | | **Preferred channel** | **Not set**, **Email**, **WhatsApp**, or **Both**. Choosing a preference does not connect an account or launch a send. | | **Only send during these hours** | Enable it to enter **From** and **Until**. The start and end must be different valid times; the audience's stored time window uses the workspace timezone. | | **Sending days** | Choose at least one day. All seven days represents no weekday restriction. | | **How the assistant should write to them** | Free-text writing guidance, up to 2,000 characters. | | **Topics they care about** | Enter a topic and use **Add topic**, or press Enter. Up to 20 distinct topics, each up to 60 characters; remove an unwanted topic with its remove control. | | **Promote to contact when they click an email** | Stores the audience's automatic-promotion preference for email clicks. It does not promote the entire audience when you save it. | These are audience settings, not a replacement for the final campaign's recipient, consent, scheduling, and approval checks. Saving this form does not send anything, and a preferred channel does not make every person eligible for that channel. ### Audience-specific fields In **Preferences** → **Fields**, use **Add field** to create a field for information specific to this audience. Supply **Field label**, **Field key**, and **Field type**: - **Text**, **Number**, **Date**, or **Choice**. - A key contains 1–40 lowercase letters, digits, or underscores; a saved key is not editable in this form. - A label contains up to 100 characters. There can be at most 40 fields in an audience. - For **Choice**, enter **Choices** and use **Add · Choices** for more, up to 50 choices. Individual choices are limited to 100 characters. - Use **Move up**, **Move down**, or **Remove** to adjust the definition list, then **Save** in the fields section. Fields created by file import also count toward the same 40-field total. Audience fields are not interchangeable with CRM custom fields: an audience-specific value belongs to that audience membership. ### Sharing The **Shared with** section is shown only with the required administrative audience rights. Shares are explicit and do not expire automatically. Removing one does not cancel separate access through ownership or workspace-paid visibility. See [Create and manage an audience](https://docs.lead-knight.com/en/audiences/create-audience/) for the steps. ## History, notes, and insights ### History **History** records supported membership and activity events, such as a person joining or leaving, becoming a contact, moving from Contacts, audience merges/splits, and recorded email activity. Each event shows its actor and time when available. **Load more** loads older events. The **Growth over the last 12 weeks** table groups joined, left, and unsubscribed totals by week. **No activity yet.** is the event-list empty state; it does not mean a message failed. ### Notes Use **Notes** for context about the audience as a whole: 1. With management access, enter text in **Add a note**, up to 4,000 characters. 2. Click **Add**. The note appears with its author and time, and the input clears after success. 3. Use **Delete note** beside an existing note if it should be removed and you have permission. **No notes yet.** is normal for a new audience. These are not the notes attached to an individual contact's CRM record. ### Insights **Insights** lists recorded sends with their subject or message excerpt, channel, date, and recipient, accepted, clicked, and unsubscribed counts. For email sends with recorded link data, **Top clicked links** shows URLs and click counts. The screen uses the workspace timezone for send dates. When no sends are returned, the tab displays **Insights appear after the first email send.** This empty-state text is not a promise that every channel or historical send has complete tracking. Selecting an audience in a draft is not itself a send or an insight record. ## WhatsApp sources: sync is not CRM promotion A connected WhatsApp account's audience-selection dialog is titled **What to keep as audiences?** It can retain people from **Groups**, **The phone's contacts**, and available **Labels**. - Select the WhatsApp groups to retain as audiences. **Search groups** and **Select all groups** help with the displayed list. - Enable **The phone's contacts** to retain people saved in that phone's address book. - For available labels, choose **Audience** or **Contacts** deliberately. The **Contacts** label option is an explicit choice to use CRM contacts, not the default meaning of keeping an audience. - Click **Save**. The confirmation says **Saved. Audiences fill in as WhatsApp syncs.** This is not an immediate guarantee that all source members have arrived. New people retained as audience members do not automatically become CRM contacts. A person already in Contacts can also be a member; the existence of that membership does not mean the sync created a new contact. **Promote to contact** is the separate member action when promotion is intended. A synced audience's header identifies the source and last sync. If the source list is empty, the dialog advises keeping WhatsApp Web open and trying again; a source that has not synced yet can show **not yet**. Do not assume that an empty retained audience contains no people in the original WhatsApp source. For connection setup, see [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/). Do not assume that simply connecting WhatsApp has automatically turned every group participant or phone contact into a CRM contact. ## Use a saved audience for WhatsApp recipients When composing a WhatsApp campaign using selected recipients: 1. Open the recipient picker's **Audiences** tab. This tab is available in selected-recipient mode, not the all-consented selection mode. 2. Review each audience name and people count, then select the required audiences. Up to 50 audiences can be selected for a send. 3. Review the selected audience chips. Use a chip's remove control to remove that audience from this send's selection; this does not delete the audience or change its members. 4. Continue through the campaign's recipient review and sending requirements. Choosing an audience alone neither sends the message nor bypasses permission, consent, or suppression checks. Audience recipients are resolved from live memberships and usable, permitted phone identities. The audience's total member count is therefore not a guarantee of the final number of sendable recipients. An audience source representing a WhatsApp group does not make this the same as posting into that group's chat. **No audiences yet.** in this picker means no saved audiences are available in the current view. Create or populate an audience first. If the list fails to load, use **Try again** rather than making duplicate audiences. ## Route paid-ad leads into an audience When the live ad editor exposes **Where leads go**: 1. Open that control for the ad and review the currently selected destination. 2. Choose **Automatic: {name}**, a listed existing audience, or **New audience…**. Creating a new audience opens the audience-name/language dialog. 3. After choosing, the routing setting saves immediately and copies that ad's existing leads into the chosen audience. It does not send email or change lead ownership. 4. Use **Add existing leads to this audience** to apply the current choice again to the ad's existing leads. Review the added, already-present, and unresolved counts shown afterward. The ad creator must be able to manage the destination audience. If that access is unavailable, choose another audience or use the automatic option. If a previously chosen audience becomes unavailable, new leads fall back to the automatic audience when it is available. This control is hidden when the API does not support it. If the paid-ads area itself is not shown in your menu, it is not enabled for your workspace; do not treat this guide as an availability promise. ### This does not change ad targeting The paid-ad editor's **Audience** step, headed **Who should see it?**, configures platform targeting such as locations and supported audience criteria. It does not select the people in a saved audience as ad viewers. Conversely, choosing **Where leads go** does not alter locations, age, interests, or platform targeting. See [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) for that workflow. ## If something goes wrong - Preferences report **Choose different start and end times and at least one sending day.**: check the time window and reselect at least one day, then **Save**. - A tab shows **Something went wrong. Please try again.**: use **Try again** in that section; an error is not the same as an empty history, notes, or insights result. - **Private contact** appears: the audience is visible but the person's CRM information is not fully shared. Audience sharing does not override that boundary. - WhatsApp audience counts differ from the eventual recipient count: check phone availability, current membership, permissions, consent, and suppression in the sending workflow. - **Audience unavailable** appears in ad routing: choose a manageable destination or the automatic option, and check the fallback warning. - A WhatsApp source does not fill immediately: check the last-sync information and the connected account rather than re-importing it as contacts. ## Related pages - [Audiences overview](https://docs.lead-knight.com/en/audiences/overview/) - [Create and manage an audience](https://docs.lead-knight.com/en/audiences/create-audience/) - [Add and manage people](https://docs.lead-knight.com/en/audiences/add-people/) - [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/) - [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/) - [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) --- # Chats and the shared inbox Find conversations from supported connected channels, understand unread messages, and distinguish customer replies from internal CRM notes and tasks. Canonical: https://docs.lead-knight.com/en/inbox/overview/ ## What this area is for **Chats** brings customer conversations from the workspace's connected accounts into one screen. You can read a conversation, reply through its original account, and work with the participant's linked CRM contact. Inbox availability depends on the connected account, the network's messaging support, and your access. A channel that supports publishing is not necessarily an inbox channel. The platform names in the filter come from the conversations actually returned; they are not a promise that every connected network supports messages here. ## Pages in this area - This overview explains the conversation list, read states, customer card, and availability limits. - [Read and reply to a conversation](https://docs.lead-knight.com/en/inbox/reply/) covers sending a reply, adding an internal note or task, and handling failures. ## Find and open a conversation 1. Open **Chats** at `/inbox`. **All conversations** shows the conversations that loaded for your workspace. 2. Enter a participant name or words from the latest message in **Search conversations…**. The search filters the loaded list; it is not a search through every message in the full thread history. 3. If conversations span more than one platform, use **All channels** to show a particular platform. Clear the search and return to **All channels** to remove both restrictions. 4. Select a conversation. Its participant name and, when available, the connected account's username appear above the messages. Check these before replying, especially when a person messages more than one business account. On a wide screen, the list, conversation, and **Customer** card appear beside each other. On a smaller screen, opening a conversation replaces the list; use **Back to conversations** to return. The first conversation can be selected automatically on a wide screen. Changing a filter does not necessarily close a conversation you already opened. ## What the conversation list shows | Item | Meaning | | --- | --- | | Participant name or identifier | Who the provider reports as the other participant. A missing name can be replaced by their identifier. | | Preview | The latest message's text, or **Attachment** when the provider reports an attachment-only preview. | | Platform icon or name | The network that supplied this conversation. An unfamiliar network can appear by name rather than an icon. | | Time or date | The conversation's update time, formatted using the workspace time zone. | | Unread number | The number of messages reported as unread for this conversation. | Unread counts are acknowledged when the conversation is actually visible, not merely selected behind the list on a phone. After the read acknowledgement succeeds, the badge clears. If that acknowledgement fails, the conversation remains readable and the badge can remain. An unread badge is not a delivery receipt for a reply you sent. Messages are grouped by day and show times in the workspace time zone. Incoming attachments may display an image or an attachment title; the reply composer itself sends text, not a new attachment upload. ## The customer card and CRM The **Customer** card can show the participant's network, account, available profile link, and permitted CRM details. **View profile** appears only when a link is available. - **Save as contact** saves a conversation participant as a CRM contact when the required identifier, supported contact channel, and permissions are available. - **Open contact** opens the existing contact. If the save detects an existing record, open that record rather than creating another one. - Phone, email, and tags depend on the saved record and your access. Seeing a participant in Chats does not grant access to another person's private contact details. - **How did they find us?** can appear for a contact saved from this screen when you have the required editing access. - **Internal note** and **Task** write to that linked CRM record. They do not send a message to the customer. Only **Reply** sends a customer-facing response. On smaller screens, the save-contact action is also offered near the composer when appropriate; the full customer side panel is not displayed. ## Available now and coming soon Reading existing conversations, sending text replies, and permitted CRM notes and tasks are available. **New message**, **Scheduled send**, and **Active automations** are marked **Coming soon**. They are not controls for starting a new conversation, scheduling a reply, or configuring an inbox automation today. ## If something goes wrong | Symptom | What to check | | --- | --- | | **No conversations yet** | Check the workspace and its connected accounts. There may be no conversations returned by the supported messaging channels yet; this is not evidence that every network has no messages. | | **No conversation matches that search.** | Clear the search and channel filter before concluding a conversation is missing. | | A warning says a platform could not load | The visible list can be incomplete even when other channels loaded. Check that account's connection and access before reloading the page. | | **We couldn't load your conversations.** | The list failed to load. Check your connection and reopen the page; do not treat the empty list as a confirmed absence of messages. | | **You no longer have access to this account.** | Ask the account or workspace owner to restore the appropriate access, or use an account you are allowed to use. Reload after access is restored. | | Notes or tasks are unavailable | Wait for the contact lookup, save or open the CRM contact, and check the relevant contact permissions. Conversation access and CRM editing access are separate. | ## Related pages - [Read and reply to a conversation](https://docs.lead-knight.com/en/inbox/reply/) - [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) --- # Read and reply to a conversation Send a text reply through a conversation's connected account, or save an internal note or follow-up task to its CRM contact without messaging the customer. Canonical: https://docs.lead-knight.com/en/inbox/reply/ ## What you will do Use **Reply** to send a text response in an existing customer conversation. Use **Internal note** or **Task** for internal CRM work instead. These are separate modes with separate text fields; writing a note is not replying to the customer. ## Before you start - Open the workspace that owns the connected account. Its channel must support inbox conversations, and you must have access to the account and the relevant messaging action. - Find an existing conversation in **Chats**. **New message** is **Coming soon**; this flow does not start a conversation with a new recipient. - For notes and tasks, the conversation must be linked to a saved CRM contact and you need write access to the relevant category. Tasks also depend on the CRM settings loading successfully. - Keep a separate copy of important unsent text before changing conversations or leaving the page. A failed send preserves the current text, but the composer is not a promise of a saved, cross-session message draft. ## Send a customer reply 1. Open **Chats**. In **All conversations**, use **Search conversations…** or, when available, **All channels** to locate the thread. The list narrows to matching participant names or latest-message text. 2. Select the conversation. The thread opens; on a phone, the conversation replaces the list. Read the participant name and account username above the messages to confirm the recipient and sending account. 3. Wait for the messages to load. Read the recent exchanges and check any attachments. If **You no longer have access to this account.** appears, stop and resolve access rather than composing a message for that account. 4. Select **Reply** and type into **Type a message…**. Only non-blank text is sent; leading and trailing whitespace is removed. 5. Press the paper-plane **Send** button. Its label becomes **Sending…** and another send is blocked while the request is in progress. 6. After the request succeeds, the text field clears and your outbound message appears in the thread. This is the app's successful-send response, not a displayed customer-read or final-delivery receipt. If sending fails, **The message wasn't sent. Your text is still here — try again.** appears and the text remains in the current conversation. Review the error, resolve the connection or account issue, and try again. Do not navigate away expecting that unsent message to be saved permanently. ## Save an internal note instead 1. In the selected conversation, wait for the CRM contact lookup. If no contact is linked and you have permission, press **Save as contact** in the **Customer** card or the small-screen composer area. A linked contact becomes available after the save succeeds. 2. If **Open contact** is offered for an existing record, use that record. If access is restricted or a duplicate belongs to someone else, ask for the appropriate CRM access rather than making another contact. 3. Select **Internal note**. Enter the internal information, up to 4,000 characters. This text field is separate from your customer reply. 4. Press **Add note**. On success, the note field clears and **Note added** appears. The note is stored against the contact, not sent to the conversation. ## Create an internal follow-up task 1. With the same saved, writable contact selected, choose **Task**. The task form appears if contact permissions and CRM settings allow it. 2. Enter the follow-up text in **Add task**, up to 200 characters. A task requires text; it is not another message to the customer. 3. Set a date and time in **Due**. Both the task text and a valid due date/time are required. 4. Review the reminder-channel controls shown for your account. The initial selection comes from your CRM task-reminder preferences; email and WhatsApp availability depend on their setup. Selecting a task reminder does not schedule an inbox reply to the customer. 5. Press **Add**. On success, the task text and due field clear and **Task added** appears. Open the contact to continue managing the task in CRM. ## Options and rules | Option | Where it goes | Important rule | | --- | --- | --- | | **Reply** | The selected customer conversation, through its original connected account | Text only in this composer; no attachment-upload control is offered. | | **Internal note** | The linked contact's CRM notes | Requires note-writing permission; a blank note cannot be added. | | **Task** | The linked contact's CRM tasks | Requires task-writing permission, loaded CRM settings, text, and a valid **Due** value. | | **Scheduled send** | Nowhere yet | Marked **Coming soon**; it cannot delay a reply or schedule a message. | The **Save as contact** action depends on a usable participant identifier and a supported CRM channel. It is not available to a workspace viewer. A saved contact does not automatically make every CRM category writable. Switching between the reply, note, and task tabs keeps their inputs separate within the open conversation. Switching to another conversation mounts that conversation's own composer; do not use this as a saved-draft workflow. ## If something goes wrong | Symptom | Likely cause and next step | | --- | --- | | **We couldn't load this conversation.** | The thread request failed. Check your connection and reopen the conversation or page before replying without context. | | **You no longer have access to this account.** | Account access changed. The inaccessible thread cannot be used for sending; ask the owner to restore access and reload afterwards. | | **Send** does nothing with an empty message | Blank or whitespace-only text is not sent. Enter a real reply. | | Sending fails but the text is still present | This is intentional draft preservation in the current thread. Resolve the error and retry; do not assume it was sent just because it remains visible in the composer. | | **Internal note** or **Task** is disabled | Contact lookup may be pending, no contact is saved, the account is inaccessible, or you lack category access. Tasks also need loaded CRM settings. | | **This conversation has no participant ID to save.** | The provider did not supply the identifier required for this save action. Work with the existing CRM record if there is one; the inbox cannot invent an identifier. | | A note or task shows an error | It has not reported success. Keep the text, address the displayed permission or validation issue, and retry. For tasks, check **Due** as well as the description. | ## Related pages - [Chats overview](https://docs.lead-knight.com/en/inbox/overview/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) - [Add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) - [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) --- # Websites and landing pages Build pages with AI, edit their content, collect inquiries and publish a website at a free or custom address. Canonical: https://docs.lead-knight.com/en/sites/overview/ ## What you can do here **Sites** brings together the creation prompt and **My sites**. Create **One page** or a **Full website**, then open the studio to review, edit and publish. Creating or saving a draft does not by itself publish it. > **Note:** If you don't see **Sites** in the menu, it isn't enabled for your workspace yet. A direct link can show **Sites isn't available in this workspace yet.** ## Find an existing site 1. Open **Sites**. 2. Under **My sites**, choose **Mine** or **Shared with me**. **All workspace** appears for roles permitted to see the workspace's sites. 3. Open the site, or use **Site actions** → **Open in editor**. 4. Check its status: **Private**, **Live**, **Unpublished changes**, **Removed** or **Building…**. The cards also show visits and leads for **30 days** when data is available. A viewer can browse but cannot create. Editing requires ownership or shared edit access; being a workspace administrator does not automatically grant editing access to every site. ## Guides in this area - [Create a page or a full website with AI](https://docs.lead-knight.com/en/sites/create-site/): description, language, photos, campaign links and website planning. - [Edit pages in the studio](https://docs.lead-knight.com/en/sites/edit-pages/): sections, blocks, text, images, shared content and page settings. - [Lead forms and booking](https://docs.lead-knight.com/en/sites/forms-and-leads/): form fields, lead destinations, notifications and booking prerequisites. - [Review, preview and publish](https://docs.lead-knight.com/en/sites/review-and-publish/): draft previews, public access and publication checks. - [Free addresses and custom domains](https://docs.lead-knight.com/en/sites/domains/): address changes, DNS connection and SSL status. ## Campaign connections A site can be linked to campaigns. In a campaign's **Landing pages**, **Create landing page** starts creation and **Connect existing site** attaches a saved site. **Main** is only a label: choosing it does not change campaign posts or ads. See [campaigns](https://docs.lead-knight.com/en/campaigns/overview/). In the real-estate edition, creation can also connect a property. Property-specific sections depend on the site's property pages; they are not general business fields. ## If something goes wrong | What you see | What to do | |---|---| | Sites are missing | Check **Mine** and **Shared with me**, and confirm you are in the intended workspace. | | Data could not load | Use **Try again**. Do not create a duplicate merely because the list failed to refresh. | | View-only access | Ask the owner to grant edit access through **Access**. | | A removed site | Opening or editing it is not proof that it can be republished; publication can be blocked for a taken-down site. | ## Create a web page with AI [Create a web page with AI](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/N1/nadlanite-en-a9b6b4ca230f.mp4) 1. Sites builds web pages for you with AI. Start on the Sites page. 2. Choose One page. 3. Describe the page you need, in one sentence. 4. Connect a property, so the page uses its details. 5. Pick the page language. 6. Click Create. 7. Before your first page, confirm you are responsible for what you publish. 8. The AI builds your page. This can take a few minutes. ## Review and publish your page [Review and publish your page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/N2/leadknight-en-79f9dc1dbe9a.mp4) 1. When the AI finishes, check the headline, images and form. 2. To change anything, just ask the AI here. 3. Check how it looks on a phone. 4. When it looks good, click Publish. 5. This will be the page’s public address. Click Publish. 6. The first time you publish, read your privacy policy. 7. Tick that you have read it, and click Confirm. 8. Your page is live. Share the address with your customers. --- # Create a page or website with AI Describe your goal, choose a language and build one page or review a multi-page plan before building a full website. Canonical: https://docs.lead-knight.com/en/sites/create-site/ ## What this is for Use the creation prompt to turn a business goal into an editable draft. **One page** starts a single-page build. **Full website** first proposes pages for you to review. The `/sites/new` entry opens the same creation screen in **Sites**. ## Before you start - Sites must be enabled for your workspace. If **Sites** is missing from the menu, it isn't enabled there yet. - You need more than viewer access to create. - Prepare the audience, offer, real business facts and action you want visitors to take. AI output still needs your review. - For a single page, have any photos ready. In the real-estate edition, you may connect an available property. ## Create one page 1. Open **Sites**. The heading **What will we build today?** appears above the prompt. 2. Under **What to create**, choose **One page**. 3. In **Describe your page**, explain who it is for, what you offer and the intended action. An example suggestion fills the prompt; edit it to match your business. Very short descriptions trigger **Describe in a few words what the page should do** rather than starting a build. 4. Optionally choose **Add photos**. Attached thumbnails appear; use **Remove photo** to remove an attachment. Up to 12 photos can be attached. 5. Optionally use **Connect to campaign**. Selected campaigns appear as removable connections; up to 50 can be selected. In the real-estate edition, **Connect property** lets you search and choose a property. 6. Choose **Page language**. Presets include **עברית**, **English**, **Русский** and **العربية**. **Other…** accepts a language code such as `fr` or `pt-BR`. 7. Click **Create**. On first use, read **Before creating your first page**, select **I accept responsibility for the pages I publish**, then **Accept**. Complete creation after acceptance. 8. The studio opens and shows build progress. Wait for the page to be ready, then check its headline, images, factual claims, buttons and form. It is still a draft: follow [review and publish](https://docs.lead-knight.com/en/sites/review-and-publish/) to make it public. ## Create a full website 1. In **Sites**, choose **Full website** under **What to create**. 2. Fill **Describe your website** with the business and pages you need. Choose **Page language** and optional campaign/property connections. 3. Click **Plan the website** and accept the first-use responsibility notice if asked. Photos are not used for a full website build; add them later in the editor. 4. In **Your website pages**, review each **Page name**, **Address** and **What is this page for?**. Change the plan before building. 5. Use **Add a page** or remove unnecessary pages. The plan allows up to 12 pages. The **Home page** cannot be removed. 6. Select **Show in the menu** only for pages that belong in navigation. The menu can show up to 8 pages; an unchecked page remains editable. Addresses use lowercase English letters, digits and hyphens and must be unique. 7. Review **Starter articles** if proposed. They are built as drafts, not published; remove unwanted ones. 8. Click **Build the website**. The progress list shows each page as **Waiting**, **Queued**, **Writing…**, **Ready** or **Failed**. Open ready pages to inspect them; use **Try again** on a failed page. 9. When **Your website pages are ready to review** appears, review all pages and shared header/footer before publishing. **Build one page instead** is available from the plan if you decide against a full website. ## If something goes wrong | Symptom | Explanation and recovery | |---|---| | Photo upload failed | Resolve the upload error and retry; do not assume the photo reached the build. | | Property no longer available | The page is not connected to that property. Choose another available property. | | Campaign links could not be saved | Retry the connection later; a site may already have been created. | | Website planning failed | The site is saved. Choose **Retry planning** or **Open in editor**, rather than creating another site unnecessarily. | | Build could not start | Stay on the plan and try **Build the website** again. | | A page has not been built yet | In its AI panel, describe the page and choose **Build the page**. | | AI allowance exhausted | Follow the displayed limit notice; the daily allowance renews tomorrow. No fixed allowance is promised here. | ## Related pages - [Edit pages in the studio](https://docs.lead-knight.com/en/sites/edit-pages/) - [Forms and lead destinations](https://docs.lead-knight.com/en/sites/forms-and-leads/) - [Sites overview](https://docs.lead-knight.com/en/sites/overview/) ## Create a web page with AI [Create a web page with AI](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/N1/nadlanite-en-a9b6b4ca230f.mp4) 1. Sites builds web pages for you with AI. Start on the Sites page. 2. Choose One page. 3. Describe the page you need, in one sentence. 4. Connect a property, so the page uses its details. 5. Pick the page language. 6. Click Create. 7. Before your first page, confirm you are responsible for what you publish. 8. The AI builds your page. This can take a few minutes. --- # Edit pages in the site studio Update sections, text, images and buttons, make AI edits, manage pages and adjust site-wide content and search settings. Canonical: https://docs.lead-knight.com/en/sites/edit-pages/ ## Before you start Open a site from **My sites**. Editing requires ownership or shared edit access. Use a computer for structure editing; the compact phone editor supports selected content but displays **Structure editing is available on a computer** for structural tools. An old version is read-only until you restore it or return to the current version. The site route opens the studio. Links to a specific page under `/sites/.../pages/...` open that page in the same studio. ## Edit content manually 1. Choose the page from the page selector. Check the page name and **Page path** so you do not edit the wrong page. 2. Choose **Manual edit**, then select text, an image or a section in the preview. Its relevant editing controls appear. 3. For text, edit **Text**. For a generated custom block, use its **Block content** fields such as **Heading**, text, images and buttons. The fields depend on the block; not every block has the same layout controls. 4. For an image, choose **Replace image**. Select from **Library** or **Upload**, add an **Image description**, then **Choose**. The preview reflects the replacement. 5. For a button, open **Edit button**, set **Button label** and **Button action**, then save. Available actions include **Scroll to a section**, **Lead form**, **Book a meeting**, **Link** and page navigation where offered. External links must use HTTPS; labels must be 1–40 characters. 6. For ordinary sections, review **Section design** and the layout, spacing or alignment options actually offered. Use **Move up**, **Move down**, **Duplicate** or **Delete section** when needed. The opening section stays first. Deleting a section saves an edit that can be recovered from an earlier version. 7. Use the section library or **Insert section here** to add content. Some sections first request media or prerequisites: a booking link, a WhatsApp number, or property-page context. Fill the starter content with real business information before publishing. 8. Check the saved-version feedback. If saving fails, keep the tab open: local edits remain, but they are not confirmed saved on the server. ## Ask AI to change a page 1. Switch to **AI**. If the page is unbuilt, describe it and choose **Build the page** first. 2. Enter **What would you like to change?**. Be specific about the desired wording, appearance or content. 3. For a targeted change, use **Point at a section** and select that section. The chosen context appears above the request. Clear it to request a whole-page change. 4. Optionally use **Add photos**, then **Send**. Wait while AI works; changing page or mode is restricted during the operation. 5. Check the new saved version. A failed AI operation leaves the last version safe. If the standard-layout notice appears, **Try the full design again** requests another attempt; a full design is not guaranteed. ## Shared content and navigation **Site content** holds **Business details**, **Services**, **Testimonials**, **Team**, **FAQ**, **Prices**, **Projects** and **Articles**. Edit real business details there rather than separately changing each bound section. **Use Site content** binds a supported section to that source; **From Site content: … · Edit** identifies a binding. Removing a content item affects bound pages when those changes are published. **Header and footer** are shared across pages. Update menu labels, destinations, logo and footer links there. The header allows up to 8 links; the footer up to 12. Changes become public through publication, not merely by opening another page. For full AI designs, header/footer design comes from the home page; edit their text/links or rebuild the home page to redesign them. ## Manage pages and settings 1. Choose **New page**, enter **Page name** and optionally **Brief (optional)**, then **Create page**. A brief asks AI to build the page in the background. 2. Open the page's options to **Rename page**, **Show in menu**, **Hide from menu**, **Duplicate page** or **Delete page** where permitted. 3. A page address uses lowercase English letters, numbers and hyphens. Changing it stops the old address immediately; there is no redirect. Home, listing and privacy-policy pages have additional locks. A page used by ad sets must first be removed as their destination before deletion. 4. Open **Settings** for **Site name**, **Page language**, phone/WhatsApp details and **Search & sharing**. Set **Search title**, **Search description**, **Share image** and **Hide from Google** as needed. A language rewrite requires confirmation and preserves previous versions; follow any restriction shown by the UI. > **Important:** Renaming an address or deleting a page can break links and ads already using it. Review those destinations first. ## If something goes wrong | Symptom | Recovery | |---|---| | View-only or old-version notice | Ask for edit access, or choose **Back to current version** / **Restore version**. | | Page changed elsewhere | **Download local JSON** before **Reload server version**. Reloading replaces unsaved local work. | | AI says the page changed | Review the latest page, then retry the request against it. | | Daily AI allowance used | Wait for the next daily allowance rather than repeatedly submitting. | | New page exists but menu update failed | Use **Show in menu** on the created page. | | New page exists but refresh failed | Reload the tab; do not create the same page again unnecessarily. | ## Related pages - [Forms and lead settings](https://docs.lead-knight.com/en/sites/forms-and-leads/) - [Review and publish](https://docs.lead-knight.com/en/sites/review-and-publish/) - [Sites overview](https://docs.lead-knight.com/en/sites/overview/) ## Review and publish your page [Review and publish your page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/N2/leadknight-en-79f9dc1dbe9a.mp4) 1. When the AI finishes, check the headline, images and form. 2. To change anything, just ask the AI here. 3. Check how it looks on a phone. 4. When it looks good, click Publish. 5. This will be the page’s public address. Click Publish. 6. The first time you publish, read your privacy policy. 7. Tick that you have read it, and click Confirm. 8. Your page is live. Share the address with your customers. --- # Lead forms, lead destinations and booking Edit form fields, decide whether submissions create contacts, choose an audience and configure notifications, replies and booking entry points. Canonical: https://docs.lead-knight.com/en/sites/forms-and-leads/ ## What this is for A lead form collects inquiries on your site. Its field editor controls what visitors fill in; **Where leads go** controls how submissions are stored. Booking is a separate visitor action that requires a booking link configured in Calendar. ## Before you start You need edit access to the site and a page containing a lead form. In **Manual edit**, select the form to open **Form fields** and the lead settings. If Sites is missing from the menu, it isn't enabled for your workspace yet. ## Edit the form 1. Select the form in **Manual edit**. The editor lists its fields. 2. Change **Field label** where needed. Name and phone are always required: their required setting cannot be turned off and those fields cannot be removed. 3. Choose **Add field** to add **Email**, **Message**, **Custom text** or **Custom choice**. Email and message are offered only when not already present. 4. For a custom choice, enter **Choices (one per line)**. Mark optional fields **Required** if visitors must answer them. 5. Use **Move up**, **Move down** or **Remove** to arrange editable fields. 6. Set **Submit button** and **Consent text**. Check that the wording matches what you actually do with the inquiry. 7. Preview the form and check its readability on desktop and phone. An editor preview submission shows **Form preview complete. No lead was sent.** It is not a real lead test. ## Choose where submissions go 1. In **Where leads go**, choose **Contact + audience** to save contacts as well as audience entries, or **Audience only** if you do not want the submission to create a contact. 2. Choose the **Audience**. **Automatic: …** uses the site's automatic audience; an available existing audience can also be selected. The site owner can use **New audience…** to create one. 3. The routing selection saves immediately. Confirm **Saved** or resolve a displayed error; the rest of the lead settings have a separate **Save** button. 4. To review contact records, open [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/). With **Audience only**, look in [Audiences](https://docs.lead-knight.com/en/audiences/overview/) instead of expecting a contact record. If the chosen audience is no longer available to the owner, the interface warns that new leads go to the automatic audience. An audience the owner cannot manage must be replaced with a manageable choice. ## Notifications, reply and after-submit behavior 1. Under **Notifications**, choose **WhatsApp**, **In-app** and/or **Email** as desired. 2. Enable **Automatic reply** only when available. It requires the site owner's Gmail sender with send permission. If unavailable, follow **Connect Gmail** where offered or ask the owner to connect their sender. 3. Fill **Subject** and **Message** for the reply. Both are required when enabled; the subject allows up to 120 characters and the message up to 2,000. 4. Under **After submitting**, choose **Thank-you page** or **Redirect URL**. A redirect must be a valid HTTPS address. 5. Click **Save** and check **Saved**. A disabled save button or validation message means the settings need correction before saving. Enabling an option is not evidence that a notification or email was delivered. Check the relevant connection and any reported error if delivery is missing. ## Add booking or a contact action 1. Configure a booking link in [Calendar](https://docs.lead-knight.com/en/calendar/overview/) before adding a booking section. 2. Return to the site editor and add the booking section, or edit a button and choose **Book a meeting**. 3. Check the destination in preview, then [publish the changes](https://docs.lead-knight.com/en/sites/review-and-publish/). For a contact button, the page needs a form or the site needs a phone/WhatsApp number. A WhatsApp section specifically needs a WhatsApp number in site settings. Do not assume that changing lead-form routing also changes Calendar booking settings. ## If something goes wrong | Symptom | Cause and fix | |---|---| | A field cannot be removed | Name and phone are protected required fields. Change their labels if necessary. | | Contact record missing | Check whether **Audience only** was selected, then inspect the chosen audience. | | Audience unavailable | Choose an audience the site owner can manage, or the automatic audience. | | Automatic reply is disabled | Gmail is disabled or the owner's sender lacks the required connection/send permission. | | Settings do not save | Check reply subject/message and the HTTPS redirect, then **Save** again. | | Booking section cannot be added | Set up the booking link in Calendar first. | ## Related pages - [Edit pages](https://docs.lead-knight.com/en/sites/edit-pages/) - [Review and publish](https://docs.lead-knight.com/en/sites/review-and-publish/) - [Sites overview](https://docs.lead-knight.com/en/sites/overview/) --- # Preview, review and publish a site Check draft pages, publish reviewed versions together and understand public access, safety review and version recovery. Canonical: https://docs.lead-knight.com/en/sites/review-and-publish/ ## Before you start You need site edit access. Build the home page first, finish placeholder content and wait for AI work to stop. If **Sites** is absent from your menu, it isn't enabled for your workspace yet. A draft saved in the editor is not the same as a public website. ## Review the draft 1. Open the site and select each page in turn. 2. Choose **Preview**, then check **Desktop** and **Phone** views. Read headings and business facts, inspect image cropping and verify buttons and destinations. 3. Test the form layout without treating it as a delivered inquiry: the editor reports **Form preview complete. No lead was sent.** 4. Check header/footer links and **Site content** because shared changes can affect several pages. 5. If needed, open **Versions**. Browse a page's history or **Site-wide** history. **Restore version** / **Restore** recovers an earlier version into the editing flow; check it again before publication. Restoring site-wide navigation, footer or colours affects every page. The built-in preview is for checking draft work in the editor. **Copy address** and **Open site** refer to the visitor address, not a promise of a public draft-preview link. A **Private** site is not on the internet; its editor is visible only to people with the appropriate access. ## Publish 1. Choose **Publish** or **Publish changes** in the toolbar. The review dialog lists changed pages and **Site-wide changes**. 2. Review exactly what is about to go live. The latest changed, built page versions and shared version are published together, or nothing is published. Untouched starter pages are not automatically finished by publishing. 3. On first publication, read **Your privacy policy**, select **I've read the privacy policy** and **Confirm** when asked. If it needs changes, use **Edit policy** before proceeding. 4. Confirm **Publish**. A private site becomes public. Wait for the review result rather than assuming the click succeeded. 5. On **The site is live**, use **Open site**, copy the address, or **Share on WhatsApp**. Open the visitor address to inspect the published result. 6. Later edits remain **Unpublished changes** until you repeat publication. ## Understand the result | Result | Meaning and next action | |---|---| | **The site is live** | The reviewed versions are published. | | **Published · flagged for review** | Publication succeeded, but the site is flagged. Read the displayed reasons; do not confuse this with a blocked publication. | | **Blocked** | The review refused publication. Fix the identified page or shared item; the batch was not published. | | **Review unavailable** | The review could not finish. Retry later; this is not successful publication. | | **Worth a look** | Review warnings such as links to unpublished pages. Such links stay hidden until their targets are published. | ## Make a site private or share editing Open **Access** to inspect **Public**, **Private** and **Who can edit**. Taking a site private asks **Take the site off the internet?**. This is different from hiding it from Google: a search setting does not make a public address private. An owner can add a teammate through **Add a team member** where permitted. Workspace administrators can see every site but edit only sites they own or that are shared with them. ## If something goes wrong | Symptom | Recovery | |---|---| | Publish is disabled | Check edit access, pending AI work, unbuilt home page and whether there are unpublished changes. | | Site changed during review | Review the refreshed versions and confirm again. The earlier confirmation is not applied to unseen changes. | | Unfinished placeholder text | Complete the affected pages and retry. | | An image is no longer available | Replace it with an accessible image, then retry. | | Privacy-policy confirmation blocks publishing | Read/confirm the policy, or edit it if the automatic check rejected it. If policy publishing is unavailable, try later. | | Site taken down | The editor cannot republish a taken-down site. Follow the displayed reason rather than repeatedly clicking Publish. | | Preview fails | Reopen the page. Do not interpret a failed preview as proof that the published address is down. | ## Related pages - [Edit pages](https://docs.lead-knight.com/en/sites/edit-pages/) - [Free addresses and custom domains](https://docs.lead-knight.com/en/sites/domains/) - [Sites overview](https://docs.lead-knight.com/en/sites/overview/) ## Review and publish your page [Review and publish your page](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/N2/leadknight-en-79f9dc1dbe9a.mp4) 1. When the AI finishes, check the headline, images and form. 2. To change anything, just ask the AI here. 3. Check how it looks on a phone. 4. When it looks good, click Publish. 5. This will be the page’s public address. Click Publish. 6. The first time you publish, read your privacy policy. 7. Tick that you have read it, and click Confirm. 8. Your page is live. Share the address with your customers. --- # Free addresses and custom domains Copy your site address, change its free label or connect a subdomain through the DNS instructions shown in the studio. Canonical: https://docs.lead-knight.com/en/sites/domains/ ## Before you start Open a site and choose **Domain**. You need edit access to change addresses. To connect your own domain, you also need access to its provider's DNS settings. If **Sites** is missing from the menu, it isn't enabled for your workspace yet. Connecting a domain does not replace [publishing](https://docs.lead-knight.com/en/sites/review-and-publish/). A private site is not public just because an address is configured. ## Use or change the free address 1. In **Domain**, find **Free address**. The displayed address is the site's label plus its platform domain. 2. Use **Copy** to copy it or **Open site** to open it. 3. To change the label, choose **Change**, enter 3–40 lowercase letters, numbers or hyphens and **Save**. 4. If **This address is taken** appears, choose another label. Privacy-policy site addresses are protected from this change. Check any links you already shared after changing an address; do not assume an old address will redirect. ## Connect your own domain 1. Under **Your own domain**, choose **Connect your own domain**. 2. Enter **Domain name**, such as `www.example.com`, and confirm. Use `www` or another subdomain; redirect the root domain at your domain provider rather than entering it here. 3. The studio displays the provider and a CNAME name and target. Copy those exact values; do not substitute a generic DNS target from an example. 4. Open DNS settings at your provider and add the displayed CNAME record. 5. Save the record at the provider, return to the studio and choose **Check**. 6. Follow the status: **Waiting for DNS record**, then possibly **Waiting for security certificate (SSL)**, and **Active** when ready. No fixed connection time is guaranteed. 7. Once active, enable **Primary address** if this should be the main visitor address. 8. Open the published site at that address and check the pages you intend to share. ## Remove a domain Choose **Remove** next to the custom domain and confirm **Remove this domain?**. Review links and ads using that hostname before removal. Removing a connection in the studio is not a domain-registration cancellation at your provider. ## If something goes wrong | Symptom | Recovery | |---|---| | Invalid hostname | Enter only the valid hostname requested by **Domain name**, not a page path. | | Waiting for DNS | Compare the provider's record name and target with the exact CNAME values shown, then **Check** again. | | Waiting for SSL | DNS connection is not the same as a ready certificate. Wait and check the displayed status again. | | Connection error | Read any detailed domain error, correct the provider's configuration and retry **Check**. | | No primary-address switch | It is available for active custom domains, not pending ones. | | Address opens no public page | Check publication and **Access**, not just DNS. | ## Related pages - [Review and publish](https://docs.lead-knight.com/en/sites/review-and-publish/) - [Edit pages](https://docs.lead-knight.com/en/sites/edit-pages/) - [Sites overview](https://docs.lead-knight.com/en/sites/overview/) --- # Photo studio: edit and reuse images Upload or choose a photo, edit it with design tools or AI, save it to the workspace gallery and use it in a campaign. Canonical: https://docs.lead-knight.com/en/photo-studio/overview/ ## What Photo studio does **Photo studio** is the workspace's shared **Saved photos** gallery and image-editing entry point. Start from an upload, stock photo or campaign photo. To generate a new image from post text, use the separate [Add media window](https://docs.lead-knight.com/en/photo-studio/add-media/) in campaign composition. Viewers can view and download saved photos, but do not get editing controls. Saving an image does not publish a post. ## Open and edit a photo 1. Open **Photo studio**. 2. Choose **Upload a photo**, **Find a stock photo** or **From your campaigns**. Upload accepts JPEG, PNG, WebP, GIF and AVIF; AVIF is converted for editing. 3. Choose the photo to open **Edit image**. A saved photo can be reopened through **Edit**. 4. Choose the tool needed for your change: | Tool | Use | |---|---| | **Adjust** / **Filters** | Change appearance and filter intensity. | | **Crop & rotate** | Set an aspect ratio, crop, straighten, rotate or flip. | | **Text** | Add wording and choose font, colour, alignment and text direction. | | **Draw** / **Shapes** | Add marks, shapes or arrows. The eraser removes drawing strokes, not the original photo. | | **Logo & images** | Add an image, workspace logo or profile photo when available. | | **Layers** | Select, move, hide, lock, duplicate or reorder added elements. | | **AI** | Request a change or remove a background with the available options. | 5. Use **Undo**, **Redo** and **Hold to compare** to review changes. 6. Choose **Save**. Wait for gallery saving and **Photo saved** before treating the gallery entry as complete. Use **Edit again**, **Download**, **Use in a new campaign** or **Done**. The editor may resize the saved image to fit the device and upload limit. If original design images are missing, it can open the saved flattened image with a notice rather than restoring every editable layer. ## Edit with AI and compare the result 1. Open **AI** and fill **Describe your change**, for example a lighting or background change. The prompt allows up to 1,000 characters. 2. Choose **Apply** and wait for the result. AI editing uses the daily AI-image allowance shown in the editor. 3. Compare **Before** and **After**. 4. Choose **Use this image** to accept or **Try again** to request another result. Generating a preview is not the same as accepting it. 5. Read any flattening confirmation before continuing: text, stickers, adjustments and cropping can become part of the new photo. AI background removal on the whole photo can clear existing layers/cropping/adjustments. Undo remains available. 6. Choose **Save** when the final composition is ready. ## Background-removal quality options - **Remove background (free, on this device)** runs locally and may first ask to download its model. - **Higher quality (uses 1 AI image)** uses one image from the daily AI allowance. Check whether the action applies to the selected image or the whole photo. Unlock a locked image in **Layers** before editing it. These are background-removal choices, not a universal quality selector for every image-generation action. ## Use photos in posts From **Saved photos**, **Use in campaign** starts a new campaign with that image. After saving, **Use in a new campaign** provides the same handoff. Review the draft and its destinations in [campaign creation](https://docs.lead-knight.com/en/campaigns/create-manual/); handing off an image does not send the post. When editing a photo selected through **From your campaigns**, a prompt can offer **Replace in campaign** or **Keep the original**. Replacement updates eligible unsent posts; already-sent posts keep the original and are not sent again. Read the replacement report and **Open the campaign** for items needing review or that changed meanwhile. Deleting a saved photo removes it from the shared gallery; photos already used in campaigns stay there. ## If something goes wrong | Symptom | Recovery | |---|---| | Gallery or preview unavailable | Use **Try again** or refresh the gallery. | | Could not save the image | Keep the editor open; edits remain there. Retry before leaving. | | Edit saved but not added to gallery | Use **Save to gallery**. The result can still be downloaded; do not mistake this for a completed gallery save. | | Daily AI image allowance used up | Try again tomorrow; ordinary editing remains a separate workflow. | | AI edit failed | Current edits are unchanged. Adjust the request and retry. | | Campaign draft is full | Remove a media file from the draft, then retry the Photo studio handoff. | | Replacement partly failed | Read the report and open the campaign. Retrying does not resend posts already updated. | ## Related pages - [Add media and generate images for posts](https://docs.lead-knight.com/en/photo-studio/add-media/) - [Video Studio](https://docs.lead-knight.com/en/video-studio/overview/) - [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/) --- # Add media and create images for a post Upload photos or videos, reuse campaign media, generate an image from the post brief and edit attachments before publishing. Canonical: https://docs.lead-knight.com/en/photo-studio/add-media/ ## Before you start Open a draft in [campaign creation](https://docs.lead-knight.com/en/campaigns/create-manual/). This guide describes its **Media** controls, not the standalone Photo studio gallery. You need write permission for changes. Write the post before generating an image from its text. ## Upload or reuse media 1. In **Media**, choose **Add media** and **Upload photos or videos**. Choose files and wait for uploading to finish; attached thumbnails appear. 2. For an existing campaign, use **From the …'s media bank** to reuse its assets. The label includes your campaign's product noun. Select available items and **Add**. Items marked **Already attached** cannot be added twice. 3. Open an attached thumbnail to inspect it. Use **Previous media** and **Next media** to review the set, **Edit** for a supported still image or **Remove from post** to detach an item. 4. Reorder attachments by dragging. With the keyboard, press Space to pick up an item, use arrow keys to move it and Space to drop it; Escape cancels. 5. Check the final set before choosing networks. A post holds up to 25 media files; a particular publishing destination can have additional rules. Removing an attachment from a draft is different from deleting a photo from the shared gallery. ## Create an image with AI 1. Write the post's content, then choose **Create an image from the text**. The **Create media with AI** dialog opens; your post text is part of its brief. 2. Fill **What would you like to see in the image?** with the visual request, up to 500 characters. 3. If available, choose **Use the photos in this post**, **Add my logo** and/or **Include my profile photo**. These controls appear only when the relevant source exists. Reference photos are eligible still images, not GIFs; up to four can be supplied. 4. Click **Create**. Wait for **Creating the image…** and the upload to complete. The generated image is added to the draft, not automatically published. 5. Open the result and check lettering, identity, factual claims and visual details. Use **Edit** if it needs changes. This dialog does not offer a general image-quality tier selector. Background-removal quality choices are described in [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/), not assumed to apply to this generation flow. ## Edit or enhance attached photos Choose **Edit** on an image to open the shared image editor. Make changes, compare and save to return the result to the post. **Auto enhance** opens a batch workflow: compare **Before** and **After**, choose the original or enhanced version, optionally add logo/profile/text overlays, then **Apply to photos**. Read the result for any photos left unchanged or not saved. When Video Studio is enabled and the relevant action is offered, video creation can hand photos into that studio. This is not available in every workspace or onboarding context. See [Video Studio](https://docs.lead-knight.com/en/video-studio/overview/). ## If something goes wrong | Symptom | Recovery | |---|---| | Asked to write the post first | Add post text before image generation. | | No logo/profile option | The corresponding workspace logo or profile photo was not available; continue without it or set it up first. | | Media bank is empty | Upload media or use another available source. The bank is specific to the existing campaign. | | Limit reached | Remove an attachment before adding another; do not assume every network accepts the full 25-file set. | | Restored draft reports unavailable media | Re-upload the missing files; the notice means they were removed from the draft. | | Enhancement partly failed | Read which photos stayed unchanged, then retry only as needed and inspect the resulting draft. | ## Related pages - [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/) - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Video Studio](https://docs.lead-knight.com/en/video-studio/overview/) --- # Video Studio projects and AI video creation Start a video with AI, an empty project or a template, review the plan and reopen projects or finished videos from the library. Canonical: https://docs.lead-knight.com/en/video-studio/overview/ ## Find your videos **Video Studio** opens the **Your videos** library. Open a project to continue work; **Load more** reveals more projects. **Video actions** offers **Duplicate**, **Delete** and **Export** where available. Deleting a project removes the project, not its media from the library. > **Note:** If you don't see **Video Studio** in the menu, it isn't enabled for your workspace yet. Direct access can show **Video Studio isn't available in this workspace yet.** Editors can create and edit; viewers can preview. Desktop projects open the hosted studio, while phones use the in-app storyboard. The layouts are different, so not every desktop layer control appears on a phone. ## Choose a starting point | Starting point | What happens | |---|---| | **Create** → **Create with AI** | Describe the video and receive an editable plan before making it. | | **Create** → **Manual creation** | Enter **Video title** and **Aspect ratio**, then **Create video** to start an empty project. | | **Start with a template** | Choose a template, fill its text and media requirements and create a project. The dialog tells you how many photos or clips are required. | Templates include general formats such as **Story**, **Special offer**, **Testimonial** and **Tips and advice**, alongside property-oriented formats. Choose content that actually matches your business rather than leaving example facts in place. ## Create a video with AI 1. Choose **Create** → **Create with AI**. 2. Fill **What should the video say?** with the story, audience, offer and verified facts, up to 2,000 characters. 3. Choose **Language**, the offered length, **Music** and **Voiceover** settings. Hebrew and English are available language choices. With voiceover, captions are included from its script. 4. Use **Choose media** for 1–30 photos and clips, inspect the selected set and remove unwanted items. Uploading is not complete while **Preparing media…** is still shown. 5. Request the plan through **Write the plan**. **Your video plan** appears with editable scenes. 6. Read each scene's line and **On-screen text**. Use **Change picture**, **Motion**, **Add scene** or **Delete** to adjust it, and reorder scenes to tell the intended story. Choose **Style**, **Voice** and **Captions** as offered. 7. Keep the plan within its constraints: at most eight scenes, lines that fit ten seconds and total estimated duration no more than 60 seconds. Shorten text or remove scenes when warned. 8. Wait for **Saved**. If saving failed, choose **Save again** before creation. **Write again** replaces your plan edits after confirmation; it is not an undo-preserving edit. 9. Choose **Create the video**. Progress reports script, voice, AI scenes, assembly and export. Wait for **Your video is ready**. 10. Review the finished result, then **Download**, **Use in campaign** or **Edit in Video Studio**. A campaign handoff does not publish the video by itself. ## Credits and availability AI options depend on the workspace, supported aspect ratio, available capability and displayed credit allowance. The library can show remaining weekly AI clips and the reset date. Use the amounts shown for your workspace; there is no universal allowance in this guide. A finished result can explicitly report that weekly AI scenes were used up and the video was made without them. Inspect the result instead of assuming every scene was AI-generated. ## If something goes wrong | Symptom | Recovery | |---|---| | Library failed to load | Choose **Try again**. | | Editor did not open | Use **Open Video Studio** to retry opening the existing project. | | Media still being prepared | Wait and try again shortly; avoid repeatedly uploading the same asset. | | Plan changed in another window | Choose **Reload** and review the new version before continuing. | | Daily video limit reached | The plan can remain saved; create it after the daily limit renews. | | Plan too long | Shorten a line or delete a scene until warnings clear. | | Video could not finish | Read the failure on the project page; do not treat a project entry as a finished export. | ## Guides in this area - [Edit, add audio and export](https://docs.lead-knight.com/en/video-studio/edit-and-export/) - [Add-media window](https://docs.lead-knight.com/en/video-studio/add-media/) - [Create a campaign](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/) --- # Edit a video, add audio and export Arrange scenes and timeline clips, add media, music, voiceover and captions, use available AI tools and export a finished video. Canonical: https://docs.lead-knight.com/en/video-studio/edit-and-export/ ## Before you start Open a project from **Your videos**. Editing requires workspace editor access; viewers get preview only. If **Video Studio** is missing from the menu, it isn't enabled for the workspace yet. Wait until uploaded media is ready. A computer opens the hosted editor with a timeline. A phone opens the scene-based storyboard. Instructions below identify the relevant surface instead of assuming the controls are identical. ## Arrange visuals 1. On a phone, choose **+ Media** to select photos and clips. On a computer, use the editor's add-media action and complete the [Add-media window](https://docs.lead-knight.com/en/video-studio/add-media/). 2. In **Scenes** on a phone, select a scene to open **Edit scene**. Adjust a photo's duration or use **Trim** with **Source start** and **Source end** for a video. Duration controls respect the limits shown for that scene. 3. Change **Scene text** and **Text style** as needed. Choose **Transition to the next scene** and **Transition duration**; choices include **None**, **Fade**, **Slide**, **Wipe** and **Zoom**. 4. Reorder scenes by dragging. Keyboard users can press Space to pick up, arrow keys to move and Space to drop; Escape cancels. Use **Delete scene** only after checking the confirmation. 5. On a computer, select the timeline clip and put the playhead at the intended cut. **Split here**, **Trim start** and **Trim end** act on the editable clip/playhead selection. Disabled controls mean that selection cannot perform the action; move the playhead or select a suitable clip first. 6. Play the video to check timing. Phone thumbnails are an alternative when live preview is unsupported; **Create a 540p preview** is offered as another preview path. Extra layers may require editing on a computer. ## Music and voiceover 1. Open **Music**. Choose from **Music library** / **Free music**, **Project audio**, **Upload audio** or **Create music** where offered. 2. Preview a track before using it. Follow any **Credit required when publishing** notice and use **Copy credit**. For uploaded or recorded audio, confirm that you own the rights or have a commercial-use licence. 3. For generated music, enter the request or choose an offered mood, review duration and cost, then **Generate** when available. 4. Open **Voiceover**. For **Text to speech**, enter **Voiceover script**, choose language and voice, review the displayed cost and generate. 5. On a phone, **Record voice** offers **Start recording**, **Stop recording**, **Use recording** and **Discard recording**. Allow microphone access. A recording can be up to 180 seconds; closing the sheet before adding it discards it. Voiceover starts at the beginning of the video. 6. Preview the whole video with audio, not just the individual track. Save the changes using the action offered by that editor. ## Captions 1. Open **Captions** and choose **Generate captions**. They follow speech in audible timeline clips; caption generation does not use AI credits. 2. Review **Edit caption text**, then choose **Caption style**, **Position** and **Text size** as offered. Correct names, numbers and any transcription errors. 3. Use **Apply changes** / **Save changes** as offered. Regenerating captions replaces your existing caption text edits and styling after confirmation. **Turn captions off** also asks before removing them. ## Available AI visuals Use only AI options enabled for the project. **Animate with AI** needs a ready photo scene; **AI clip** creates a new clip from a request. Available choices can include **Duration (seconds)**, **Quality** and sound. Where multiple tiers are offered, **Lite**, **Standard** and **Premium** are capability-dependent choices, not a promise that every tier is enabled. Review the cost quote and remaining credits before **Generate**. Unsupported aspect ratios, missing source media, read-only access or insufficient credits can disable generation. The result is added when ready; check the actual insertion or replacement message on the surface you are using. **Restyle with AI** / clip editing marked **Soon** is not an available action and is not part of this workflow. ## Save, export and use the result 1. Wait for **Saved** or complete **Save changes**. Do not leave while the editor reports unsaved changes. 2. Wait for pending AI clips to finish; they block export. 3. Choose **Export** and the offered **Resolution**. The desktop export dialog offers 720p and 1080p. 4. Start export and keep the tab open. For device export, keep it in front on a computer or the page open and screen on on a phone. If device export is unsupported or fails, the interface can report a server export instead. 5. Wait for the finished preview, play it and inspect audio, captions and visuals. An export progress message is not yet a finished file. 6. Choose **Download** for the video file. **Use in campaign** can first save a locally created result to the account; follow any saving/uploading status before continuing. Once stored, the desktop action can read **Open new campaign**. 7. Review the campaign draft and publication settings. A valid linked-campaign handoff can return to that campaign; otherwise a new campaign is started. Exporting or handing off does not itself publish. ## If something goes wrong | Symptom | Recovery | |---|---| | Save failed | Changes remain on screen. Use **Retry saving** before leaving. | | Conflicting changes | **Download my changes** before **Load latest**; the editor cannot safely merge concurrent work. | | AI cost unavailable | Retry the cost check; do not assume generation is free. | | Generation failed | Retry or remove the pending item. If retry details are missing, remove it and start a new generation. | | Microphone unavailable | Allow access or use text-to-speech; unsupported browsers cannot record. | | Export failed | Ensure media is ready and edits saved, then retry. | | Text behind subject blocks export | Keep that effect within 20 seconds per video and use Chrome/Edge on desktop or Android, or disable the effect. | | Download link unavailable | Use **Refresh download link** where offered. A ready render can exist even when its link cannot be loaded. | ## Related pages - [Video projects and AI planning](https://docs.lead-knight.com/en/video-studio/overview/) - [Add-media window](https://docs.lead-knight.com/en/video-studio/add-media/) - [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/) --- # Add photos and clips to a video Use the video media picker or separate add-media window to attach uploaded, recent, Photo Studio or stock media to a project. Canonical: https://docs.lead-knight.com/en/video-studio/add-media/ ## What this window does The video's media picker collects photos and video clips for a project. The desktop editor can open a separate **Choose photos and clips** window at a project's add-media route. Adding assets to that project is different from publishing a campaign or exporting a finished video. ## Before you start Open the intended video project and stay in its workspace. You need write permission; a viewer sees **This video is read-only. You can't add media.** If **Video Studio** is not in the menu, it isn't enabled for that workspace yet. ## Select and add media 1. In the video creation flow choose **Choose media**, on a phone choose **+ Media**, or open the desktop editor's add-media action. The picker or separate window shows **Choose photos and clips**. 2. Choose the source: | Source | What to select | |---|---| | **Upload** | Use **Choose files** to select accepted image or video files. Wait for upload/preparation rather than closing while it is still running. | | **Recent** | Reuse available recent media in the workspace. | | **Photo Studio** | Pick a saved photo. This source supplies images, not video clips. | | **Stock** | Enter a stock-photo query and **Search**. This is an image source, not stock video. | 3. Select the intended items and check the selected-item count. Use **Load more** where offered to find more media. A caller that accepts only video does not offer image-only stock choices. 4. In a regular picker, choose **Use selected media**. It returns the selected assets to the calling creation/editor flow; inspect that flow before proceeding. 5. In the separate add-media window, choose **Add to video**. Wait for **Added. You can close this window.** The window attempts to close automatically; if it stays open, you can close it after the success message. 6. Return to the project. Review the imported media and arrange it in the [editor](https://docs.lead-knight.com/en/video-studio/edit-and-export/). Attaching a source asset does not imply that a finished video has been exported. ## If something goes wrong | Symptom | Cause and recovery | |---|---| | No media found | Change source or stock query, or upload a file. | | Thumbnail unavailable | A preview could not be shown; verify the selected asset before relying on it in the video. | | Media failed to load | Retry loading; do not assume the project has received anything until the add action succeeds. | | Video not found in current workspace | Return to the project's actual workspace and reopen its add-media action. | | No permission to add media | Ask for workspace edit permission; opening the window alone does not grant access. | | Window did not close | Close it manually only after **Added. You can close this window.** appears. An error is not a completed addition. | ## Related pages - [Video Studio overview](https://docs.lead-knight.com/en/video-studio/overview/) - [Edit and export](https://docs.lead-knight.com/en/video-studio/edit-and-export/) - [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/) - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) --- # Paid ads Find your way from connecting an ad account to preparing, approving, measuring and managing a paid campaign. Canonical: https://docs.lead-knight.com/en/paid-ads/overview/ ## Where paid ads live Paid ads are part of your campaigns, not a separate replacement for posting. A post can supply the text and media for a paid ad. The campaign board shows its paid cards alongside the campaign's content, while **Analytics** → **Paid ads** brings together accounts, results, forms, permissions and settings. If you do not see **Paid ads**, it is not enabled for your workspace yet. The platforms and actions offered also depend on workspace availability, the connected account, its permissions and the ad's current state. A visible platform or a connected account does not by itself mean an ad is ready to launch. ## Choose the right guide | What you want to do | Guide | |---|---| | Sign in to an ad platform, choose accounts, set tracking, sharing and spending caps | [Connect and configure an ad account](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) | | Turn a post or campaign idea into an ad, choose its goal, prepare creative and forms, set a budget and publish | [Create and launch a paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/) | | Select actual locations, city radii, interests, Reddit communities and Meta placements | [Choose locations and targeting](https://docs.lead-knight.com/en/paid-ads/targeting/) | | Read account totals, delivery states and the results of individual posts; pause, resume, change a budget or delete | [Understand results and manage spending](https://docs.lead-knight.com/en/paid-ads/results/) | | Change an eligible running Meta ad, add ads or replace a lead form without confusing drafts with platform changes | [Manage live Meta ads](https://docs.lead-knight.com/en/paid-ads/manage-live-ads/) | ## Platforms you may see The paid-ad editor has platform-specific options for **Facebook & Instagram**, **Google**, **TikTok**, **LinkedIn**, **Pinterest**, **X**, **ChatGPT** and **Reddit**. Only the platforms enabled for your workspace appear as available connection choices. The connection screen calls Facebook and Instagram **Meta**, and calls the ChatGPT connection **OpenAI**. The same content does not have the same capabilities everywhere. For example, TikTok needs a vertical video, X uses text-only ads, and Pinterest and ChatGPT use a photo. Native lead forms, WhatsApp destinations, calls, tracking, location types and live editing depend on the platform. Always read each platform's destination and missing-details messages in **Review** rather than assuming one platform's settings apply to the others. ## Draft, approval, checking and delivery are different - **Save draft** saves your setup; it does not approve spending. - **Publish** opens the publishing flow. Review any operations-fee and privacy confirmations, then the account-specific budget and spending confirmation. - **Waiting for approval** means an ad-account owner still needs to approve a request. It is not the platform's policy review. - **Checking & sending** means checking and submission are in progress. The editor tells you that the ads were sent for checking; it does not promise that they are delivering. - **In review**, **Rejected** and **Not delivering** describe platform-side conditions that need separate attention from a saved or approved draft. ## Understand who pays Ad spend is charged directly by the advertising platform to the connected ad account. Managing paid campaigns through LeadKnight also has an operations-fee agreement. The confirmation describes a fee of 10% of actual platform-reported spend, plus VAT, charged on the third of the following month. Read the displayed terms before agreeing; a workspace sponsor may need to authorize your paid campaigns separately. Budgets, account spending limits, weekly protection and monthly caps are not interchangeable. Reporting is delayed, so a daily amount or a cap is not a guarantee of an exact final charge. [Results and spending management](https://docs.lead-knight.com/en/paid-ads/results/) explains the warnings and pause reasons. ## Related areas - [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/) for the content and campaign board that paid ads build on. - [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/) for other kinds of connected accounts. - [Analytics](https://docs.lead-knight.com/en/analytics/overview/) for reporting outside the paid-ad area. - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) for following up on leads. - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) for billing setup and payment-card issues. --- # Connect and configure an ad account Connect an advertising account, select the accounts you can use, and configure permissions, tracking, result sharing, privacy and monthly caps. Canonical: https://docs.lead-knight.com/en/paid-ads/connect-ad-account/ ## What this is for An ad account is the advertising account that pays the platform and owns the ads. Connecting a social publishing account is not the same as choosing an ad account. Use this guide before [creating your first paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/), or when an existing account needs reconnecting. ## Before you start - Use a workspace where paid ads are available. If you do not see **Paid ads**, it is not enabled for your workspace yet. - Have access to the advertising account on the platform you want to connect. Only accounts available to that login can be selected. - Allow popups for the app. Most platforms open their sign-in flow in a separate window. - For Meta, have a Facebook Page you manage and include it in Facebook's permission selection. A personal Facebook login alone does not meet the Page requirement. - Decide who on the team should be able to use the account. Sharing does not transfer spending approval to the team. ## Connect the account 1. Open **Connections** and find **Paid ads**. Choose the platform tile you want. You can also reach Connections with **Connect an ad account** from **Analytics** → **Paid ads**. 2. In **Connect ad account**, choose **Sign in to** the displayed platform. Complete the permissions in the popup. The dialog shows **Sign in**, **Choose accounts** and **Done**, with a waiting message while sign-in is unfinished. 3. If a second sign-in step appears, use the additional **Sign in to** button marked as step 2 and complete that window too. Do not treat completion of the first window as completion of the connection. 4. Wait for **Choose ad accounts**. Select one or more usable accounts, then choose **Use selected**. An unavailable account cannot be selected. Selecting none leaves you unable to continue. 5. Look for **Your ad accounts are connected.** The dialog lists the connected accounts and explains that tracking setup starts automatically. Choose **Manage ads** to continue in paid-ad analytics, or **Close**. After sign-in, the popup normally closes and the original dialog continues. If the return opens as a full page, it returns to Connections so account selection can continue there. A window closing is not, by itself, proof that accounts were connected: look for the account-selection or connected state. ### Connecting ChatGPT through OpenAI When the **OpenAI** connection is offered, a new connection uses **API key** instead of the usual sign-in button. Enter the key, then choose **Connect ad account**. The field accepts 10–500 characters; this is an input limit, not proof that a key is valid or that an advertising account is eligible. The screen states that the key is sent securely to the provider and is not saved here. The onboarding ad-account tiles do not include this key-based connection. Use Connections when it is available to your workspace. Do not paste the key into ad text, a support conversation or a knowledge-base search. ## Configure the connected account Open **Analytics** → **Paid ads** → **Settings**. Each account shows its name, platform, who connected it and its connection status. Account settings are editable by the connected account's owner when their workspace permissions allow changes. ### Account on or off Use **Account on** / **Account off** to allow or prevent new ads from that account. > **Important:** Turning an account off does not pause ads already running. To stop delivery, use **Pause** on the paid campaign. Disconnecting has different consequences, described below. ### Monthly cap 1. Choose **Edit monthly cap** on the account. 2. Enter the cap in the account's currency. Use a valid non-negative amount; leave it empty for **No cap**. 3. Choose **Save** and check the displayed cap and **Spent this month**. The account cap is not a separate budget for each ad. The reporting delay means it is not a guaranteed hard charge ceiling. The spending confirmation explains that reported monthly spend reaching 105% of the cap pauses ads, and final reported spend can be higher. See [spending controls and pause reasons](https://docs.lead-knight.com/en/paid-ads/results/). ### Pixel and conversion setup Tracking setup starts automatically after connection. Under **Settings**, read the account's current message: **Setting up the pixel…**, **Pixel linked**, **Pixel created**, a prompt to choose a pixel, or **Pixel setup didn’t finish.** When **Pixel setup** is available, open it and select an existing pixel or create one if that platform offers creation. For Reddit, create the pixel in Reddit Ads Manager first, then return and choose it. Do not keep trying to create a Reddit pixel inside LeadKnight. Some platforms do not support pixels through this flow and show that explicitly. ### Sharing results with the platform 1. Open the account's result-sharing control, shown as **Result sharing is on** or **Result sharing is off**. 2. Read **Share results with** the platform and the authorization statement. 3. Choose **All my contacts (recommended)** or **Only contacts from ads and pages**. 4. Decide whether to also enable **Also use them to personalize ads (audiences and retargeting)**. 5. Choose **Turn on**, or **Not now** if you are not ready to authorize sharing. The screen describes sharing New lead, Qualified, Meeting held, Won and Not relevant results for ad measurement. Lost status is not sent. Google needs a verified secondary conversion action; Not relevant reports wait until it is verified. TikTok may ask you to create an offline event set in TikTok Events Manager before retrying. If sharing is blocked because there is no conversion destination, open **Pixel setup** and resolve that first. Having a connected account is not equivalent to having working conversion sharing. Website conversion optimization and Meta quality-lead options can require this setup. ### Who may use the account Open **People & approvals**. An account owner can manage **Who may use this account** and pending spend approvals. Shared members can see spend and results, prepare ads and request spending approval. Only the account owner approves launches, resumes and budget raises. Account ownership is not the same as being an administrator of the workspace. If the screen says only the account owner may manage access, ask the person named as having connected the account to make the change. ### Privacy policy In **Settings**, workspace owners and admins can set **Custom privacy policy link (optional)**. Use a full `https://` address. Leave it empty to use the default privacy-policy page when available, and use **View default policy** to review it. Save the change and look for **Saved**. A lead form needs an effective privacy policy. A default policy may require your confirmation before publishing. The form's **Privacy link text** is the wording people click, not the policy URL. ## Reconnect or disconnect - **Needs reconnecting**: in **Settings**, choose **Reconnect**, finish the sign-in and selection flow, then check that the account shows **Connected**. - **Disconnect**: read **Disconnect ad account?** before confirming. It pauses ads created in LeadKnight on every ad account in that connection and cancels pending spend approvals. This is a connection-wide action, not just removal of one tile or one draft. ## If something goes wrong | Symptom | Likely cause shown by the app | What to do | |---|---|---| | Sign-in never opens | Popup blocked | Allow popups and start sign-in again. | | No account choices appear | No ad accounts are available to this login | Verify the login and account access in the platform, then reconnect. | | Meta asks for a Page | No managed Page was included | Create a Page if needed, or select the Page in Facebook's permissions and try again. | | The login is already connected by someone else | The connection belongs to another team member | Use the existing account through its owner and sharing settings rather than trying to claim the same login. | | An account cannot be selected | The account is unusable | Read the reason next to it and resolve that condition in the platform. | | A platform is missing or reported unavailable | It is not available for this workspace | Use an available platform; connection does not unlock an unavailable platform. | | Connection fails with an add-on or payment message | The provider account lacks the required add-on or payment setup | Resolve the stated provider-account requirement before reconnecting. | | **Sync needs attention** appears | Account detail synchronization needs attention | Check the account's status and any error in paid-ad settings; do not assume missing details mean the account is ready to spend. | | Result sharing cannot be enabled | Missing or unverified conversion setup | Resolve **Pixel setup** or the platform-specific conversion instruction, then retry. | | Settings are read-only | You are not the connected account's owner, lack workspace permissions, or are in a read-only context | Have the account owner make the change. | ## Related pages - [Paid ads overview](https://docs.lead-knight.com/en/paid-ads/overview/) - [Create and launch a paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/) - [Understand results and manage spending](https://docs.lead-knight.com/en/paid-ads/results/) - [Connections and destinations](https://docs.lead-knight.com/en/channels/overview/) --- # Create and launch a paid ad Prepare a paid ad from campaign content, choose its destination, creative, form, audience and budget, then review and confirm the launch. Canonical: https://docs.lead-knight.com/en/paid-ads/create-paid-ad/ ## What this is for Use a campaign post or an idea's posts as the source for advertising. The editor prepares the platform-specific ad and keeps the paid results connected to your campaign. Saving the setup is separate from approving its spend. ## Before you start - [Connect an ad account](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) that you own or are permitted to use. A connection must be usable, and the platform must be available for your workspace. - Have source content with suitable text and media. If an AI campaign is still writing its posts, the editor can defer text and media requirements until generation finishes; inspect the finished ads before publishing. - For a LeadKnight-page destination, have a published page. For a website destination, know the full `https://` address. For WhatsApp or calls, know the business number including `+` and its country code. - For lead forms, review your privacy policy and decide which questions and permissions you need. - Know the account's currency, available budget and who approves spending. A shared account may require its owner's approval. Operations-fee, billing-card or sponsor requirements may also apply. If paid-ad choices are absent, the feature is not enabled for your workspace yet. Do not assume a regular publishing connection enables advertising. ## 1. Open the paid-ad editor 1. Open the campaign and find the source post. Open its actions menu and choose **Promote with a paid ad**. For an idea or folder, the corresponding action is **Promote**. 2. Alternatively, while composing content, select a paid-account tile under **Also run it as a paid ad** and complete **Set up ad**. This embedded setup is draft-only: finish with **I'm done**, then use **Review and launch** after the post and paid setup have been saved. 3. The dialog opens with **Step by step** or **Quick plan**. Step by step separates **Platforms**, **Goal**, **Ad**, **Lead form** when relevant, **Audience**, **Budget** and **Review**. Quick plan opens the same settings through the highlighted parts of one sentence. 4. Choose **Save draft** whenever you want an explicit saved draft. **Draft saved** confirms that save. It does not start the ad or authorize a charge. ## 2. Choose platforms and accounts 1. In **Platforms**, choose one or more available platforms. 2. Choose the **Ad account** for each selected platform. If none is connected, use **Connect** and complete the connection flow. 3. Read any account error or unavailable message before continuing. Choose **Continue** after an account is selected. The editor contains choices for **Facebook & Instagram**, **Google**, **TikTok**, **LinkedIn**, **Pinterest**, **X**, **ChatGPT** and **Reddit**, but availability is workspace-dependent. Already launched platforms are locked here; changes apply only to platforms that are not running yet. ## 3. Choose what people should do | Choice in Goal | Details to supply | What to check before continuing | |---|---|---| | **Get a form filled** | Native form where supported; otherwise a published LeadKnight page | Read each platform's destination in Review. Do not assume the same form is supported on every platform. | | **Send people to my page** | **Which page?** → **Choose a published page** | A page marked **Not published** must be published before launch. | | **Website link** | **Website address** and **Optimize for** | Use a full `https://` URL. Choose **Visits** or **Sign-ups and leads**. Conversion optimization may require result sharing for the account. | | **Start a WhatsApp chat** | **Business phone number** | Include `+` and the country code. Check whether a selected platform falls back to your page. | | **Get calls** | **Business phone number** | Include `+` and the country code. Read any page-fallback message for other platforms. | For destinations outside LeadKnight, the editor warns that leads and cost per lead cannot be tracked there. Website conversion guidance specifically describes leads recorded in your LeadKnight CRM, not every action on an arbitrary external website. For eligible Meta form campaigns, **Leads likely to become customers** may be offered. This requires result sharing and verified Meta quality-lead readiness. If the option is unavailable, use standard leads rather than assuming that enabling sharing alone unlocks it. This optimization is separate from choosing a form with an extra review step. ## 4. Prepare the creative 1. Open **Ad** and choose **Edit ads** to inspect the ad text for the source posts. Resolve variations such as `a|b` into one actual version; unresolved variations block **Publish**. 2. Check **Headline**, **Description**, **Button** and **Photo or video**. The shared headline field allows up to 255 characters and the description up to 500; platform-specific fields can have tighter limits. 3. If a multi-photo format is offered, choose **Carousel** or **Separate ads**. A carousel is one swipeable photo ad; separate ads share that platform's budget. A carousel needs at least two photos, no videos, and is unavailable for WhatsApp or call goals. The selected-media controls allow up to ten items for the multi-media formats. 4. Reorder selected media using the reorder controls. Carousel cards can have an optional **Title (optional)** of up to 40 characters. 5. Open each tab under **What each platform needs**, complete its fields and inspect **Preview**. On a smaller screen, use the **Preview** button to switch between editing and previewing. The platform may display the ad differently from the preview. ### Platform-specific creative | Platform | What to prepare | |---|---| | Meta | Suitable media and ad text. **Let Meta improve your ad** allows cropping, brightness changes and small text changes using your own words and pictures. It does not create a fixed allocation of budget per creative. | | Google | Choose **AI campaign across Google** or **Search ads only**. Provide 3–15 **Short headlines**, up to 30 characters each. Descriptions are up to 90 characters: 2–4 for Search, 2–5 for the cross-Google campaign. **Business name** allows 25 characters. The cross-Google type also needs its long headline and required picture choices; Search needs at least one search word or phrase. | | TikTok | Choose a **Vertical video** from source media and complete **Short caption**, up to 100 characters. Wait for the video-shape check; an unconfirmed vertical format must be replaced. | | LinkedIn | Complete **Intro text**, up to 3,000 characters, **Headline**, up to 200, and the relevant image or offered multi-photo format. | | Pinterest | Use a photo, a **Title** up to 100 characters and **Description** up to 500. | | X | Complete **Ad text**, up to 280 characters. Ads are text only; source photos and videos are not sent. | | ChatGPT | Use a photo and complete its headline and description. Ads for an individual home for sale or rent are blocked. In a real-estate workspace, the required non-property acknowledgement must be true; do not check it for an ad that is actually about one home. | | Reddit | Complete **Post title**, up to 300 characters. Use one source post and one ad: one photo or a photo carousel, not a set of separate ads. Set up the account's Reddit pixel before launch. | For Google, **Write the rest for me** can prepare text assets when the source text and business name are available. Review generated text and required pictures yourself; generation is not publication or approval. ## 5. Configure a lead form when offered The **Lead form** step appears for a form goal with Meta or LinkedIn selected. The editor has native-form controls for both, but a platform's current capabilities can still route a form goal to a LeadKnight page or block launch. In particular, do not rely on the LinkedIn form labels alone as proof that native forms are enabled. Follow the platform-specific destination and validation shown in **Review**. 1. Choose **Create a new form**, **Use a form you made before**, or **Start from a copy**. For an existing form, select the account if needed and then the form. Its questions and screens stay as created in the platform. 2. For a new form, complete **Form name**. When offered, choose **More leads** for a shorter submission path, or **More serious leads** for an extra review of contact details. This is a form experience, not a promise of lead quality. 3. Under **What should the form ask?**, use **Add a contact detail** or **Add your own question**. New forms allow up to 15 questions. Custom questions use **Pick an answer** or **Short answer**; finish the question and every answer choice. Date-and-time questions are not available. 4. Mark relevant multiple-choice answers as **Good fit** when you want corresponding leads labeled in the CRM. Reorder or remove questions with their controls. If LinkedIn reports an unsupported question or contact field, remove it rather than assuming Meta's form support applies. 5. For Meta, decide whether to use **Confirm phone numbers by text**. If Meta refuses this, the app asks for explicit acknowledgement before launching without that check. 6. If offered, turn on **Ask permission to email** and review **Email permission wording**. The permission checkbox is optional and unchecked by default; submitting the form does not require agreeing to email marketing. 7. Expand **Intro**, **Thanks** and **Privacy policy**. Review the optional introduction, thank-you screen, button and website. Choose **Language** and check the privacy link. **Privacy link text** allows up to 70 characters and should say something like “Privacy policy”, not contain the web address itself. 8. Inspect the form preview, including contact details, review and thank-you states. If no policy is available, use **Open settings** and resolve that before launch. ## 6. Set the audience Open **Audience** and choose actual locations from the search results. Typed search text alone is not a selected location. Add at least one location and check the audience mode, housing rules and platform notes. For the full picker workflow and limits, follow [Choose locations and targeting](https://docs.lead-knight.com/en/paid-ads/targeting/). When an ad contains several ideas, select each idea to inspect its own audience. **Apply to all ideas** copies the selected audience to the other ideas; use it only when the same audience is appropriate for all of them. ## 7. Set the budget and dates 1. Open **Budget**. Choose **Per day** or **Total for the whole run**. 2. Choose **Split it for me** to allocate one total between same-currency accounts, or **Set each platform myself** to enter each amount. Different account currencies require separate platform budgets; the editor does not convert them into a shared total. 3. Enter a positive amount with the decimal precision allowed by the account's currency. Review each account's displayed **Minimum**. If no minimum is available, the app says it will check before launch; do not substitute an assumed minimum. 4. Check the **Monthly cap** and spent amount. Lower a share that exceeds the remaining cap, or have the account owner change the cap when appropriate. 5. Under **Start**, choose **Start now** or **At a date**. Under **End**, choose **Keep running** where available, or **At a date**. A total budget requires an end date, and the end must be later than the start. 6. Review any amounts marked **Already committed — locked**. Existing launched allocations cannot be silently reassigned by editing the unlaunched part of the plan, and the total cannot be less than the committed budgets. For grouped Meta ideas, **Review** shows one campaign with multiple ad sets sharing its campaign budget. Meta decides how to allocate that budget; it is not a fixed amount per ad. For non-grouped platforms, Review can show separate campaigns and the amount per idea. Read that actual breakdown before approving. ## 8. Review, publish and confirm spending 1. Open **Review** or **Review and launch**. Check each platform's account, destination, ad or carousel count, audience, budget and schedule. 2. Read **Saved settings**. A new ad can inherit settings from your last ad, including form choices, destination, button and housing classification. Use **Change** for any inherited value that does not fit this campaign. 3. Use **Fix** on every missing-detail message. If **Publish** is disabled, resolve the blocker rather than looking for a way to skip checking. 4. Read any Meta remaining-funds warning. The account's money or spending limit can run out before your ad's chosen budget, and other ads use the same account funds. Use **Open Meta Ads Manager** to add funds or adjust the account spending limit when appropriate. 5. Choose **Publish**. This is the current submission entry point; there is no separate **Check** button in this editor. Checks and submission follow the confirmed publishing flow. 6. Review and accept the operations-fee terms if requested. Resolve any billing-card, unpaid-fee or workspace-sponsor requirement. Review the default privacy policy and confirm it if requested. 7. In **Confirm launch**, inspect every account, budget, start, end and spending warning. Confirm with the button shown, such as **Confirm weekly budget of** the displayed amount, **Confirm and launch**, or **Launch and spend**. Cancelling here does not authorize the launch. 8. Look for the next state. An owner-approval request shows **Waiting for approval**. An accepted submission tells you the ads were sent for checking, or shows **Checking & sending**. These are not guarantees of platform approval or delivery. Return to the paid card or [Results](https://docs.lead-knight.com/en/paid-ads/results/) to follow the outcome. A daily amount is an average, not a hard daily charge cap. The confirmation explains weekly protection: at 105% of the reported weekly budget the ad is paused until Sunday, then resumes automatically. Monthly cap protection also uses 105% of reported spend. Reporting delays can make the final amount higher. Read the actual account-specific confirmation before authorizing spend. ## If something goes wrong | Symptom | Cause to check | Fix | |---|---|---| | Continue will not advance | Missing account or required details in the current step | Select an available account, or complete the listed details. | | Publish is disabled | Missing locations, budget, creative, policy, dates, or unresolved text variations | Follow **Fix**; use **Edit ads** to write one text version. | | A platform sends people to a page instead of the chosen action | That action is unsupported for the platform or currently unavailable | Select a published page and confirm the actual destination in Review. | | Google assets are incomplete | Headline, description or required pictures are missing | Open Google's tab and complete its fields and minimum asset counts. | | TikTok video is refused | The video was not confirmed as vertical | Choose a verified vertical source video. | | SMS confirmation is refused | Meta will not allow the text check for the account | Review the warning and choose **Launch without the text check** only if you explicitly accept that change, then retry publication. | | Budget is refused | It is below the account minimum, over the cap, invalid for the currency or missing an end date | Correct the specific amount, cap, currency or date message. | | Ads were submitted but are not running | Owner approval, platform review or a delivery problem is still outstanding | Inspect the paid card and Results; do not create another ad merely because submission succeeded without delivery. | | Draft save failed | The paid setup was not saved successfully | Use **Try again**. In the composer, a saved post can exist even when saving its paid setup failed; do not assume both were saved. | ## Related pages - [Connect and configure an ad account](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) - [Choose locations and targeting](https://docs.lead-knight.com/en/paid-ads/targeting/) - [Understand results and manage spending](https://docs.lead-knight.com/en/paid-ads/results/) - [Manage live Meta ads](https://docs.lead-knight.com/en/paid-ads/manage-live-ads/) - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) --- # Choose locations and targeting Use the location, interest, Reddit and placement pickers to define an audience, understand AI expansion and respect housing restrictions. Canonical: https://docs.lead-knight.com/en/paid-ads/targeting/ ## What this is for The **Audience** step sets the locations and supported audience choices for an ad. It is not a box for a free-text description of your ideal customer: locations, interests and communities must be chosen from their actual results. A platform can use audience hints differently from another platform, and AI hints are not strict restrictions. ## Before you start - Open a [paid-ad draft](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/) and choose its platforms and ad accounts first. Search choices depend on the selected account. - Decide the locations where the business can actually serve customers. - Decide whether the content concerns housing. In the real-estate edition, keep the housing classification and the actual content in agreement; do not change it to bypass restrictions. - If editing a running Meta idea, read [the live-ad rules](https://docs.lead-knight.com/en/paid-ads/manage-live-ads/) first. Its audience mode is locked and stricter Advantage+ constraints apply. ## 1. Select the audience to edit 1. Open **Audience**. The page asks **Who should see it?** 2. If the plan has several ideas, select an idea by name. Its audience settings appear below. 3. Edit that idea's settings. Use **Apply to all ideas** only if you want to replace the other ideas' audiences with this one. Inspect the individual ideas again before launching. ## 2. Choose actual locations 1. Under **Where are your customers?**, use **Search a city, region or country**. Enter at least two characters when searching the connected account's location catalog. 2. Choose a result from the list. Read its location type and country code to distinguish, for example, cities with the same name in different countries. 3. After selection, the search clears and a location row appears. That row, not the typed query, is what is included in the audience. 4. Repeat for other locations. The picker permits up to 50 selected locations and prevents choosing the same location twice. 5. For an incorrect location, use **Remove** on its row. Keep at least one location selected; an empty audience is blocked before launch. If the selected platforms have no supported general location-search account, the picker uses **Search a country** and a country list. It does not let you turn a typed city into a supported location. Reddit targets countries here; ChatGPT uses country targeting. Review every platform's supported-location messages when combining platforms. ### Set a city radius City rows have **Distance around** and a **km** / **mi** unit selector. A non-housing city can be **City only** with the radius empty. When a radius is set, the field accepts whole numbers from 1 to 80 in the selected unit. Housing has a higher minimum: 25 km or 15 mi, with the same maximum of 80 in the selected unit. Changing the unit changes the unit of the setting; check the resulting number instead of assuming it was converted to the same physical distance. Out-of-range numeric entries can move to the allowed limit when saved. Read the displayed value again after saving or continuing. ## 3. Choose how the audience is found ### Let AI find people Choose **Let AI find people (recommended)**. Locations remain part of the setup, while supported hints guide the platform rather than imposing a strict audience boundary. Meta explicitly warns that it may show the ad beyond the hinted audience when it expects better results. - Meta uses hints and can look further for likely responders. - Google's Performance Max uses the goal, assets and destination; the editor says audience hints are not sent to Google. - TikTok can use smart targeting beyond your hints. - LinkedIn can expand the audience and optimize creative rotation. - Pinterest, X and ChatGPT use the supported locations without a promise of automatic audience expansion. - Reddit uses countries and any selected communities and conversation keywords; no automatic expansion is promised. ### Choose the audience yourself Choose **I’ll choose who sees it**. Where offered, set **Minimum age**, **Maximum age**, **Gender**, **Interests** and **Languages**. The general draft age fields allow 13–65, and maximum age cannot be below minimum age; this is an editor input range, not a guarantee that every platform or ad category accepts those ages. Reddit-only plans do not offer age or interest targeting. Manual Reddit audiences can use gender and languages alongside countries and Reddit-specific targeting. Housing removes age and gender choices. Always read the note for each selected platform: unsupported choices do not become supported merely because a shared field is visible. ## 4. Select interests and behaviors 1. Under **Optional audience hints** in AI mode, or **Interests** in manual mode, inspect **Suggested for your business** when suggestions are available. 2. In **Search interests or behaviors**, type at least two characters. Choose an actual returned interest or behavior; merely leaving text in the search does not add it. 3. For Meta, **Browse categories** opens the available categories. Expand a category and choose an item from it. 4. Confirm that chosen items appear as removable selections. Up to 200 can be selected, and duplicate selections are disabled. 5. If shown, read **Audience size** as the platform's supplied estimate, not a guaranteed delivery count or number of leads. If the search is disabled, check that you selected a platform and account that support targeting search. Do not interpret missing suggestions as a requirement to invent or manually type an interest ID. ## 5. Configure Reddit communities and keywords For a Reddit account, use **Reddit communities and keywords** rather than generic interests. 1. Type at least two characters in **Search Reddit communities**. 2. Select a returned `r/` community. It appears as a removable selection. The displayed member count, when available, describes the returned community, not your campaign's guaranteed reach. 3. In **Conversation keywords**, enter a word or phrase and choose **Add**, or press Enter. 4. Repeat as needed. The picker permits up to 50 communities and 50 keywords; each keyword is 1–100 characters after trimming. Keywords that differ only by capitalization are treated as duplicates. 5. Remove an unwanted community or keyword with its remove control. You can leave both lists empty and let Reddit choose. This does not remove the need for countries, suitable creative or the Reddit pixel setup. ## 6. Choose Meta placements when offered In a manual Meta audience, open **Where should the ad appear?** - **Automatic (recommended)** lets Meta choose supported placements. - **Choose the places** opens placement checkboxes. Options include Facebook Feed, Stories and Reels; Instagram Feed, Stories and Reels; Messenger Inbox; and Partner apps. - Keep at least one supported placement or return to Automatic. Forms only appear in placements that support forms; listing a placement does not guarantee that this particular goal can use it. These placement controls are not a request to choose Instagram or Facebook organically. They are placement settings for the Meta paid ad. ## Housing restrictions With **Yes, it’s about housing**, Meta's housing audience uses ages 18–65 and all genders, with no ZIP-code targeting. City radius must be at least 25 km / 15 mi. Other platforms have their own housing rules. For the real-estate edition, turning housing off requires every selected location to be in Israel. Adding locations outside that permitted set can restore the housing classification and its restrictions. A country-only picker does not bypass the classification. ## 7. Review the result Return to **Review**. Check each platform's locations and whether it shows **People the AI finds**, **Chosen by you** or **Launched audience**. The last one refers to the saved audience of an already launched platform, not new edits to an unlaunched one. For grouped ideas, inspect every idea's summary. ## If something goes wrong | Symptom | Cause to check | Fix | |---|---|---| | Search gives no choices | Too-short query, a failed search or no matching catalog result | Use at least two characters, refine the name or country, and use **Try again** for a load error. | | A typed location disappears but no row appears | No result was selected | Search again and click the actual result. | | Only countries are available | No supported general location-search account is selected, or the platform uses country targeting | Choose a country; do not expect a city or ZIP field on every platform. | | A search result cannot be added | It is already selected or the selection limit was reached | Remove an existing selection first if you need to replace it. | | ZIP codes disappear or radius increases | Housing rules are applied | Use supported housing locations and at least the required city radius. | | A field is locked | The platform has launched, housing rules apply, or the current live audience mode does not support it | Edit only the supported fields. For a different live Meta mode, create a new campaign rather than forcing an update. | | A platform rejects the audience | A shared selection is unsupported by that platform | Follow its specific location or targeting warning and check the account's platform settings. | ## Related pages - [Create and launch a paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/) - [Manage live Meta ads](https://docs.lead-knight.com/en/paid-ads/manage-live-ads/) - [Understand results and manage spending](https://docs.lead-knight.com/en/paid-ads/results/) - [Paid ads overview](https://docs.lead-knight.com/en/paid-ads/overview/) --- # Understand results and manage spending Read paid-ad metrics and delivery states, investigate ads that are not delivering, and use the permitted pause, resume, budget and delete actions. Canonical: https://docs.lead-knight.com/en/paid-ads/results/ ## What this is for Use **Analytics** → **Paid ads** for account-wide reporting and supported spending actions. Use the campaign's paid cards to inspect the paid campaign, its ideas and where its budget went. Both views can show a platform delivery problem even after a launch request was accepted. ## Before you start - Use the workspace that contains the connected ad account and campaign. If **Paid ads** is missing, it is not enabled for that workspace yet. - Have permission to see the account's money and results. A campaign collaborator can see a paid card without being allowed to see spending or manage the ad account. - For recent launches, allow for platform reporting and synchronization. A missing value is not proof of zero spend or no delivery. - Know which account and currency you are reviewing; amounts in different currencies are not merged into a single converted total. ## 1. Read account results in Analytics 1. Open **Analytics**, choose **Paid ads**, then **Results**. 2. Set **From** and **To**. The initial range is the first day of the current month through today in the workspace's time zone. The start date must not be after the end date. 3. Use the retry button if a request failed or you want to reload the current range. A valid date range is required. 4. Choose **Choose metrics**. Select between one and eight metrics, then **Save**. The saved choice determines which totals you see. 5. Read **Totals** separately for each currency. Then inspect each account's **Spend this month**, **Monthly cap** and **Last synced** information. The selected-period totals and the current-month account spend are different views; changing the date filter does not turn the monthly cap into a cap for that filter. 6. Under **Running ads**, inspect **Ad / campaign**, **Status**, **Budget**, leads and cost per lead. The list includes ads created outside LeadKnight, marked **Created outside** LeadKnight. An external campaign does not automatically gain LeadKnight's management buttons. 7. Use **Open in** the platform when an external link is provided to inspect that campaign in its own advertising manager. ### What the metric choices mean | Metric | How to use it | |---|---| | **Spend** | Reported advertising spend for the results being shown. Do not confuse it with the chosen budget. | | **Leads** and **Cost per lead** | Compare lead results with their acquisition cost. They are not the same as clicks or every platform-reported conversion. | | **Meetings** and **Cost per meeting** | Follow the meeting results attributed to the ads. | | **Won**, **Revenue** and **ROAS** | Follow downstream business outcomes recorded for ad leads, not only delivery metrics. ROAS is displayed as a return multiple. | | **Impressions** | Ad displays, not a count of unique people. | | **Clicks**, **CTR** and **Cost per click** | Examine interaction and click efficiency; a click is not a lead. | | **Platform conversions** | Conversion results reported by the advertising platform; do not assume they equal CRM leads. | Unavailable results appear as **—** or **Not available**, depending on the view. Do not read either as a measured zero. For WhatsApp, calls and activity outside LeadKnight, the editor warns about limits to lead and cost-per-lead tracking. ## 2. Inspect a campaign's paid card 1. Open the campaign board and select a card or row marked **Paid**. 2. Before launch, the card shows its budget and ad count. After launch, where available, it shows spend against the chosen daily or total budget, leads and cost per lead, ROAS and reach. 3. Open the card for exact amounts and additional results: **Spend**, **Leads**, **Cost / lead**, **Meetings**, **Cost / meeting**, **Won**, **Revenue vs spend**, **ROAS** and **Reach**. 4. Expand **Platform numbers** for **Impressions**, **Clicks**, **CTR**, **CPC** and **Platform conversions**. 5. Expand **Where the money went** to see spend and leads for source posts or photos. An empty result states that results appear a few hours after the ad starts. A load error offers **Retry**. 6. If an ad has several creative versions, read the combined-results notice. These are results across versions, not the exact spend of only the creative currently displayed. 7. If **Ideas** are listed, inspect their audience summaries, spend and lead results separately. **No ideas running** means that none of the idea switches is currently on; a parent campaign existing does not mean an idea is serving. If you cannot see money, the details view can show only the paid status and ad count. Have the account owner review sharing permissions instead of treating the hidden figures as missing platform data. ## 3. Understand status and delivery The campaign board and Analytics use some different labels for the same stage. Read the current status together with any platform note and pause reason. | Status or message | What it tells you | What to do next | |---|---|---| | **Draft** | Setup exists but has not been launched | Complete [creation and review](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/). | | **Waiting for approval** | The connected account owner must decide on the spend request | The owner reviews it in **People & approvals** or the paid campaign's approval dialog. | | **Approved** | A request has been approved | Follow checking, submission and delivery; approval alone does not prove the ad is showing. | | **Checking & sending** / **Launching** | Processing and submission are underway | Read the next state rather than creating another campaign. | | **In review** | The platform is reviewing the submitted ad | Check the platform's status. No review completion time is promised. | | **Live** / **Running** | The ad has reached the running stage | Still inspect delivery issues, dates, idea switches and spend. | | **Not delivering** / **Stopped by** the platform | The ad is not currently serving, even if its internal campaign state reached Live | Open its details and follow the specific platform reason and fix link. | | **Rejected** | A platform rejection is reported | Read its reason. Use **Edit ads** where offered or correct the issue in the platform. | | **Paused** | Delivery has been paused | Read whether it was by you, the assistant, a cap, a lost connection or the platform before deciding to resume. | | **Ended** / **Completed** | The paid run ended | Review its results; do not assume Resume is available. | | **Failed** | Launch or another requested action failed | Read the actual error and correct it before **Try again**. | | **Not reported** | No recognized status has been supplied | Inspect synchronization and the platform; it is not confirmation of Live or Failed. | | **Archived** / **Deleted** | The platform reports that state | Review in the platform; do not assume an old result row remains editable. | ## 4. Diagnose an ad that is not delivering 1. Open the paid card and read the latest error, **Platform note** or **Stopped by** notice. 2. If Meta asks for account verification, use **Verify your account in Ads Manager** when offered. Complete Meta's steps in the affected account, then return to inspect delivery again. This is different from reconnecting an expired login. 3. If Meta refuses lead ads because of its Lead Ads Terms, a Page admin must accept them for the ad's Facebook Page. Use **Accept the Lead Ads Terms on Facebook**, then retry the failed publication after acceptance. 4. If account funds or the account spending limit are insufficient, open the platform's billing and payment settings. Increasing the ad budget alone does not add account funds. 5. If the card says a cap or weekly budget caused the pause, follow the spending-control rules below. 6. If the connection is lost, [reconnect the account](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) before attempting an action that requires it. 7. If the platform provides another refusal, follow that wording and its **Open Ads Manager** link where available. A generic retry without correcting the cause is not a fix. Do not treat zero spend as the diagnosis by itself. A future start, review, paused ideas or delayed metrics can produce different next steps. Check the status and schedule before changing the creative or creating another paid campaign. ## 5. Pause or resume when permitted ### Pause the whole paid campaign In Analytics, choose **Pause** on an eligible ad and confirm **Pause this ad?**. The confirmation explains that the platform will stop running it and that it can be resumed later. From the campaign board, open the paid card and use **Pause** where shown. Pause is offered for permitted live or launching paid campaigns. Keep following the result of the action; a button press is not a reason to ignore a refusal or pending platform operation. ### Pause an individual idea In the paid campaign's **Ideas** list, use **Pause** for the relevant idea. It can show **Pausing…**, then **Paused**. A failed change is shown as **Pause failed · retry** with **Retry pause**. Resume has equivalent pending and failed states. An idea switch does not override a paused parent campaign. If every idea is off, the details show **No ideas running**. Resume the intended idea and, when appropriate, the parent campaign; do not assume switching one on has resumed the other. ### Resume 1. Choose **Resume** on a paused paid campaign when the action is available. A valid saved budget and no conflicting pending operation are required for this action to appear. 2. Review fee requirements if shown, then read **Confirm resume** and its account, budget and dates. 3. Confirm with **Launch and spend** if you can approve, or **Ask** the named owner **to approve** when approval is needed. 4. Check whether the request is waiting for owner approval or whether the campaign has resumed. Resume is a spending action, not merely a local switch. An archived campaign cannot launch or resume paid ads, although existing running ads can still be paused. ## 6. Change a live or paused budget 1. Choose **Change budget** on an eligible live or paused paid campaign. It is unavailable while a conflicting operation is pending. 2. Check **Previous budget** and the account currency. Enter the new amount and inspect its minimum. 3. Change **End date** only when the platform supports it. The current editor supports this for Meta; other platforms show that changing a running ad's end date is unsupported. An existing end date cannot be removed, and a total budget still requires an end date. 4. Choose **Change budget** to reach the spending review. A raise may require the fee agreement and account-owner approval; a decrease does not require agreeing to the fee just to reduce spend. 5. Read the updated spending warning. Confirm using the button shown and check the resulting state. If account data or a monthly projection cannot be loaded, resolve that error rather than assuming the confirmation was sent. A budget change does not automatically mean that every paused idea is now running. For Meta, the campaign budget is shared across ideas and ads; raising it is not a fixed allocation to the specific creative you are viewing. ## Weekly protection and monthly caps The daily-budget confirmation displays a weekly budget equal to seven daily amounts and explains that the platform may spend more on some days. At 105% of the reported weekly budget, LeadKnight pauses the ad until Sunday and resumes it automatically. A pause can read **Weekly budget used · resumes Sunday**. - Wait for Sunday if you want that automatic resume. - Use **Keep paused** from the paid campaign details if you want it to remain paused instead. - A budget raise can require renewed approval and remains subject to the account cap and fresh spend data. The account's monthly-cap protection also pauses ads at 105% of reported spend. The cap, weekly protection and platform account funds are different controls. Platforms can report spend with a delay of up to a few hours, so the final amount can exceed a threshold. A cap is not an exact real-time charge guarantee. ## 7. Delete only what you intend to delete From a paid card's details, **Delete** appears only when management is allowed and the operation state permits it. - For a draft, read the irreversible draft-deletion confirmation. - For a launched paid campaign, read **Delete paid campaign?**. The campaign is stopped on the platform first and then removed from LeadKnight. Existing results and leads are kept. Confirm with **Delete campaign** only if that is the intended outcome. - If the platform does not confirm the stop, deletion is not completed. The error says it stays paused here; inspect the platform and retry after the indicated wait instead of assuming it was deleted. Deleting an individual ad, deleting a paid campaign, turning an account off and disconnecting the connection are distinct actions. [Live Meta ad management](https://docs.lead-knight.com/en/paid-ads/manage-live-ads/) explains individual-ad removal; [account settings](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) explains disconnection. ## If something goes wrong | Symptom | Cause to check | Fix | |---|---|---| | No visible accounts | No owned or shared ad account is visible | Connect an account or ask its owner to share it. | | No rows for a date range | The platform reported no campaigns in that range | Check the dates and workspace, then inspect the platform if needed. | | Spend has not synced | Metrics are not current | Check the last-sync message and wait for fresh reporting. Do not read missing data as zero. | | Budget raise or launch is refused because reporting is stale | Spend is still catching up | Wait for fresh metrics; changing the cap does not fix stale data. | | Management buttons are absent | Permissions, status, an external campaign or a pending operation limits actions | Use the connected account owner or the platform; do not assume every listed campaign can be edited here. | | Pause or resume of an idea failed | The platform did not confirm that switch | Read the error and use the specific **Retry pause** or **Retry resume** control after resolving it. | | A spending action asks for Billing | Card, unpaid fee or billing setup is missing | Use **Open Billing**, resolve the stated requirement and retry. | | A spending action asks for a sponsor | Sponsor permission or updated fee terms are missing | Ask the workspace sponsor to authorize the action or accept the terms. | | Another action is running | The account has a conflicting operation | Let it resolve before making a new request. | | Results differ from the visible creative | Results combine several creative versions | Read the combined-results notice and inspect the platform for more granular reporting. | ## Related pages - [Create and launch a paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/) - [Connect and configure an ad account](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) - [Manage live Meta ads](https://docs.lead-knight.com/en/paid-ads/manage-live-ads/) - [Analytics](https://docs.lead-knight.com/en/analytics/overview/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) --- # Manage live Meta ads Edit eligible Meta ads, add creative, manage idea audiences and lead routing, or replace a lead form with explicit platform and owner confirmations. Canonical: https://docs.lead-knight.com/en/paid-ads/manage-live-ads/ ## What this is for An eligible running or paused Meta paid campaign can open **Edit ads on Meta**. This shows the ads actually sent to Meta, not just the source posts. Changes here do not rewrite your original campaign posts. Nothing is sent until you confirm the requested change. This is not a promise of live editing on every platform or every Meta creative. When an ad is not editable, inspect its status and the platform rather than treating draft editing as a way to change a launched ad. ## Before you start - Open the correct campaign's paid card and use **Edit ads**. An eligible Meta campaign in the live or paused state opens the live editor. - Have management permission for the connected account. A shared-account change can still require its owner's approval. - Read any pending-operation or lead-settings-replacement notice. A request already in progress can block new edits or additions. - Identify what you want to change. Creative, an idea's name and audience, the campaign budget, lead routing and lead-form replacement are separate operations. - For budget changes, parent pause/resume or deletion of the whole paid campaign, use [Results and spending management](https://docs.lead-knight.com/en/paid-ads/results/), not a creative-edit request. If the feature or an action is missing, it may not be enabled for your workspace or permitted for this account, format or state. ## 1. Inspect the actual ads 1. Open **Edit ads on Meta** and let the current ads load. 2. Inspect each ad's media, text, headline and state. Use **Open Meta** when provided to compare with the platform. 3. Read any combined-results notice. Results can combine multiple creative versions and do not necessarily show the exact spend of only the displayed version. 4. Use **Check status** when current status is uncertain or a request is still awaiting confirmation. Failed inputs and unsent edits are kept when the refresh cannot load the latest ads. ## 2. Edit creative and submit only the intended changes 1. Edit a permitted ad's **Headline** and **Ad text**. For a live edit, text must be non-empty and within the displayed limit; the live creative editor permits up to 63,000 body characters and 255 headline characters. Unresolved text variations such as `a|b` are not allowed. 2. Use **Replace photo or video** if you need new media. Each edited ad needs exactly one image or video. Wait for uploads to finish before submitting. 3. For bulk text work, select the ads and choose **Replace text**, **Find & replace**, **Add at start**, **Add at end**, **Set headline** or **Back to post text**, then **Apply to selected**. Applying this operation changes the local editing values; it does not itself submit to Meta. Inspect the resulting text on the cards. 4. Check the selection before **Update on Meta**. If some ads are selected, only edited ads within that selection will be sent. If the selection is cleared, all edited ads are included. A request supports at most 50 edited ads; other unsent edits can remain for a separate request. 5. Choose **Update on Meta**. In **Confirm changes on Meta**, compare **Before** and **After** for every requested ad. 6. Confirm **Update on Meta**, or cancel to keep editing. The request covers only the changes listed; other ads, destinations, parent switches and budgets stay unchanged. 7. Follow the result. **Awaiting account-owner approval**, **Waiting for Meta confirmation**, **Confirmed on Meta**, **Not applied** and **Outcome not confirmed** are different outcomes. A request accepted for processing is not yet a confirmed change. ### Closing with unsent changes Closing a dirty editor asks **Discard unsent changes?** Choose **Keep editing** to retain them or **Discard changes** to lose edits that have not been sent. Discarding does not cancel requests already sent to Meta. ## 3. Change an idea's name or supported audience 1. From an ad's actions, choose **Edit idea** when available. 2. In **Edit idea on Meta**, check the **Idea name** and audience. The change applies to every ad in that idea, not to other ideas or the campaign budget. 3. Use the real [location and targeting pickers](https://docs.lead-knight.com/en/paid-ads/targeting/). The existing audience mode cannot be switched between manual and AI through this live update. 4. For an Advantage+ idea, treat interests as suggestions. Maximum age, gender, languages and manual placements are unavailable in that mode, and minimum age cannot exceed 25. 5. For a housing idea, keep its classification and restrictions: ages 18–65, all genders, no ZIP targeting, and city radius at least 25 km / 15 mi. 6. Choose **Update on Meta**, compare the before/after summary and confirm. Inspect the request state or owner approval afterwards. A new audience mode requires a different campaign setup rather than overriding the existing idea's locked mode. ## 4. Add ads to the existing campaign 1. Open **New ad** when it is offered. 2. Choose media. Each photo or video becomes its own ad; the form accepts one to ten media items. 3. Complete **Headline** and **Ad text**. In this addition form, headline allows 255 characters and body text allows 10,000. Both need content and neither can contain unresolved text variations. 4. Choose **Ad set**. Select an available existing ad set or **New ad set**. A new ad set needs a shared campaign budget; the campaign supports up to 20 ad sets. For a new one, complete **Name** and its audience. 5. Choose **Add ad**. Read any fee requirement, then the **Add ads** confirmation, including the target and number of ads. 6. Choose **Confirm addition**. New ads go through Meta review. If the campaign is paused, adding them does not resume it; they can run only after the campaign is resumed and Meta review allows it. 7. Inspect the addition state. **Waiting for approval**, **Sending to Meta**, **Not added**, an owner decline or an unconfirmed result require different next steps. The campaign budget is shared by existing and new ads. Meta may move some allocation to new ads; adding ten creatives does not mean authorizing ten independent copies of the campaign budget. If **New ad** is disabled in a draft because it uses selected photos as a carousel or one ad per photo, the message asks you to return to a single-ad setup first. Do not confuse this draft format restriction with live Meta eligibility. ## 5. Remove an individual ad Use **Remove ad** only when the action is permitted. Read the confirmation: the ad is stopped on Meta and removed from active ads, while past results and leads are kept. Other ads, the idea, campaign and budget stay unchanged. Confirm and follow the operation's state. For a draft ad or a confirmed failed addition, removal has different wording: the source post stays on the campaign board. An unconfirmed addition is not proof that nothing was created, so inspect Meta before retrying or treating it as a failed local draft. ## 6. Choose where leads go When **Where leads go** is available in the live editor, it controls the CRM audience receiving this ad's leads. This is different from the targeting audience that sees the ad. 1. Choose **Automatic** with the displayed audience name, an available audience, or **New audience…**. 2. Read the result after selecting. This choice saves immediately and copies existing leads to the chosen audience; it does not send email or change lead ownership. 3. Use **Add existing leads to this audience** to apply the current choice to existing leads again when needed. Read the counts for added, already present and unresolved people. 4. If the chosen audience is no longer available, read the fallback warning. New leads use the automatic audience when it is available. The ad creator must be able to manage the chosen audience. If the app refuses it, choose another manageable audience or Automatic. See [Audiences](https://docs.lead-knight.com/en/audiences/overview/) for the CRM side of audience management. ## 7. Replace a Meta lead form safely **Change form and optimization** is offered only for eligible campaigns. Despite the title, this replacement keeps the campaign's current optimization. Meta has one optimization per campaign; changing that optimization requires a new campaign. 1. Apply or discard unsent ad edits first. They must not be mixed with a lead-settings replacement. 2. Choose **Change form and optimization** and inspect **Optimize for**. It shows the current optimization that will stay unchanged. 3. Prepare the new form, including its name, questions, answers, email-permission wording when enabled, thank-you screen and privacy policy. Use the same form rules described in [Create and launch a paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/). 4. Choose **Review replacement**. Inspect the complete list of affected ideas and ads and the new form preview. 5. Read the warnings: replacement ads are created in the same Meta campaign, their learning restarts, and old ads stop only after Meta explicitly approves all new ads. The campaign budget is unchanged and shared by old and new ads; Meta may change allocation, and a daily budget is not a hard charge cap. Meta determines the review time. 6. Confirm the acknowledgement, then **Confirm replacement on Meta**. A connected account owner may still need to approve the request. 7. Follow **Lead-settings replacement**, its review reasons and the approved/switched counts. **In Meta review**, **Switching**, **Switched**, **A decision is needed**, **Outcome not confirmed**, **Cancelling** and **Cancelled** are distinct states. Paused campaigns and ideas stay paused. Replacing settings is not confirmation that ads are delivering. During a replacement, further edits, additions and replacement requests are unavailable until it is resolved; emergency pause remains available from the campaign. If **Cancel replacement** is permitted, read the cancellation notice and confirm **Confirm cancellation**. Only replacement ads are stopped. Originals are not resumed or changed, and cancellation itself may remain in reconciliation before it completes. ## If something goes wrong | Symptom | What it means or what to check | What to do | |---|---|---| | **Outcome not confirmed** or receipt could not be confirmed | Meta may already have applied the change | Use **Check status** and **Open Meta**. Do not send another edit or replacement request. | | **Not applied** or some changes failed | Some requested changes were not confirmed as applied; successful ads can already be refreshed | Inspect each result and the retained failed inputs before a new attempt. | | The saved ad changed | Your editing snapshot is no longer current | Check status, load the latest ad and review it before making a new request. | | Owner declined the request | Approval was refused | Review the saved inputs and resolve the owner's concern before another request. | | A live creative cannot be updated | Format, destination or original link is not safely supported | Use the platform and read the specific restriction. Removal may still be available if permitted. | | The replacement form is not ready | Meta has not finished preparing it | Wait, then retry the same request as instructed; do not create a second replacement. | | Meta refuses the replacement's phone text check | SMS confirmation is not allowed | Use **Continue without phone confirmation by text** only after explicitly accepting that change. | | Replacement is only partly switched | Cutover is still reconciling; only confirmed predecessor stops count as switched | Check status and Meta. Do not treat an intermediate count as completion. | | Approval is unavailable because replacement details are missing | The immutable request summary is not available in that view | Do not approve from a saved draft as a substitute. Use a view containing the actual request details or get help. | ## Related pages - [Create and launch a paid ad](https://docs.lead-knight.com/en/paid-ads/create-paid-ad/) - [Choose locations and targeting](https://docs.lead-knight.com/en/paid-ads/targeting/) - [Understand results and manage spending](https://docs.lead-knight.com/en/paid-ads/results/) - [Connect and configure an ad account](https://docs.lead-knight.com/en/paid-ads/connect-ad-account/) - [Audiences](https://docs.lead-knight.com/en/audiences/overview/) --- # Settings Find assistant controls, account preferences, business information, workspace time zone, developer connections and billing. Canonical: https://docs.lead-knight.com/en/settings/overview/ ## Find the right section Open **Settings** in the app. The page groups controls by purpose; on smaller screens, the section buttons at the top jump down the page. There is no single Save button for the whole page: each card either saves its own form or saves a switch when you change it. | Section or card | What belongs here | | --- | --- | | **Assistant** | Learned information, remembered rules and facts, writing style, approval preferences and WhatsApp messages from the assistant. | | **Account preferences** | **Sign-in methods**, interface preferences and notification delivery. | | **Business identity** | Business name, industry, goals, description, knowledge for AI writing and logo. | | **Business details** | Business address, phone and email used in email contact details. | | **Advanced** | Workspace **Time zone**, and developer API keys and webhooks when available. | | **Billing** | **Open billing**, which opens the separate billing page. | ## Business and workspace settings - [Tell the AI about your business](https://docs.lead-knight.com/en/settings/business-details/): distinguish the business description and AI knowledge from the business contact lines. - [Set the workspace time zone](https://docs.lead-knight.com/en/settings/time-zone/): check the stored zone rather than assuming it follows your computer. - [Sign-in methods and notifications](https://docs.lead-knight.com/en/settings/sign-in-and-notifications/): manage a password and choose email or WhatsApp notification delivery. Business identity and business contact details are editable by workspace owners and admins. Other members see a read-only version. These are workspace settings, not a replacement for your personal profile; see [Your account](https://docs.lead-knight.com/en/account/overview/). ## Language and appearance Under **Account preferences**, find **Preferences**. 1. In **Language**, choose **English** or **עברית**. This changes the interface language and text direction. 2. In **Appearance**, choose **Light** or **Dark**. These controls do not switch between the general and real-estate editions. The edition belongs to the workspace. ## Assistant controls The [Assistant guide](https://docs.lead-knight.com/en/assistant/overview/) links to detailed instructions for the controls inside **Assistant**: approvals and automatic publishing, memory and learned information, writing style, and chatting or giving tasks. **WhatsApp messages from your assistant** controls reminders before meetings, idle-contact alerts, the morning briefing and quiet hours. This is separate from the **Notifications** card under **Account preferences**. WhatsApp settings depend on an available channel and a connected account; follow the connection prompt if it appears. ## Developer API keys and webhooks Scroll to **Advanced**. When enabled, **Developer API** contains **Your API keys**, **Create API key**, the **API base URL** and **API documentation (OpenAPI)**. **Webhooks** contains **Your webhooks** and **Add webhook**. These connect your own server to the workspace. Keys and signing secrets must stay on your server, never in public browser code, URLs or a shared document. Follow [Developer API](https://docs.lead-knight.com/en/developers/developer-api/) for the actual setup and security requirements. If you do not see **Developer API** or **Webhooks**, it is not enabled for your workspace yet. Existing keys or webhooks may remain visible for revocation or deletion even when new use is disabled. Do not mistake a disabled creation control for an empty list. For the separate AI-connector topic, see [AI connector](https://docs.lead-knight.com/en/developers/ai-connector/); do not use an API key as a substitute for an unavailable connector. ## Billing Under **Billing**, select **Open billing**. Changes to plans, payment methods and billing are handled on that page, not in the settings cards. See [Plans and billing](https://docs.lead-knight.com/en/billing/overview/). ## If something goes wrong - A card is still loading: wait for its controls before editing; each card loads independently. - A load error appears: use **Retry** where offered. A failed load is not proof that saved information was deleted. - A save error appears: the change was not confirmed. Keep the page open, correct any highlighted field and try that card again. - Business fields are read-only: ask a workspace owner or admin to change them. Switching interface language does not change permissions. ## Assistant settings: memory, writing style and approvals [Assistant settings: memory, writing style and approvals](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/M4/nadlanite-en-348904e0695c.mp4) 1. In Settings, the Assistant section shows what the assistant has learned and remembers about you. 2. To shape how it writes for you, click Add preference. 3. Describe your style in a few words, and save. 4. It now writes in your style, for you only. 5. Approvals decide whether it publishes on its own. Off means every publish waits for you. 6. Once WhatsApp is connected, it can also send reminders and a morning briefing. ## Tell the AI about your business [Tell the AI about your business](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P5/nadlanite-en-7b1ce8f14694.mp4) 1. Your office’s details are in Settings. Scroll down to Business identity. 2. Here are your business name, industry, goals and office size. 3. Under What the AI should know, add the facts that make your office different. 4. Click Save. 5. AI writers use this knowledge whenever Business info is selected. ## Set your workspace time zone [Set your workspace time zone](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P6/nadlanite-en-df3745276d77.mp4) 1. Scheduled posts go out by your workspace time zone. In Settings, scroll down to Time zone. 2. Click Change. 3. Open the list and search for your city. 4. Pick your time zone. It saves right away. 5. Scheduled campaigns now publish at times in this time zone. ## Sign-in methods and notifications [Sign-in methods and notifications](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P7/nadlanite-en-ed9ca67d4869.mp4) 1. Your sign-in and notification choices are in Settings. 2. Sign-in methods shows the email and accounts you sign in with, like Google. 3. To also sign in with a password, click Set or change password. 4. Notifications decide where alerts reach you, besides the bell. 5. Turn email notifications off if you only want them in the app. 6. WhatsApp alerts need a connected WhatsApp number first. --- # Tell the AI about your business Save business identity and AI writing knowledge, then add the contact details used in your business emails. Canonical: https://docs.lead-knight.com/en/settings/business-details/ ## What this is for **Business identity** holds the information that describes your business. Its **What the AI should know about your business** field is the longer source of business facts used by AI writers when **Business info** is selected. Use it for facts the writer should know, not just a short slogan. **Business details** is a separate card for the address, phone and email used in business email contact details. Your business name is edited in **Business identity**, so you do not need to enter it twice. ## Before you start - Check that you are in the correct workspace. These details describe that workspace's business. - You must be an owner or admin to change either card. Other members can read the information. - Prepare the correct business name, factual description and any logo you want to use. Do not put passwords or API keys in the AI knowledge field. ## Save your business identity 1. Open **Settings** and scroll to **Business identity**. Wait for the existing details to load. 2. Check **Business name**. A non-empty name is required to save. 3. Choose **Industry**. When using the other-industry option, fill **Other industry** with your own description. 4. Under **What do you want to achieve?**, select the goals that fit: **Grow your social presence**, **Get leads**, **Use AI agents** or **Run paid ads**. These describe your goals; selecting a goal does not itself launch an ad or send a message. 5. Set **Office size** if relevant. The choices are **Just me**, **2–5 people**, **5–15 people** and **15+ people**; the blank choice leaves it unspecified. 6. Fill **About your business** with a concise description. 7. In **What the AI should know about your business**, add the facts the writer should use. For example, describe your services, intended customers and the claims you can support. These examples are suggested content, not additional required fields. 8. If needed, use **Logo** to choose an image. A preview appears while the upload is processed. **Remove logo** removes the selected logo from the form. 9. Select **Save**. Wait for **Business details saved.** before treating the update as saved. ## Field rules | Field | Rule shown by the editor | | --- | --- | | **Business name** | Required to save; up to 200 characters. | | **Other industry** | Up to 200 characters. | | **About your business** | Up to 2,000 characters. | | **What the AI should know about your business** | Up to 20,000 characters. The counter shows how much you have used; an over-limit value blocks saving. | | **Logo** | Choose an image; selecting a preview is not the same as a successful save. | The AI knowledge field and your writing style serve different purposes. Business knowledge supplies facts. Writing style controls how the writer should sound. Workspace rules and personal memories are also managed separately; see the [Assistant guide](https://docs.lead-knight.com/en/assistant/overview/). ## Save business contact details 1. Scroll to **Business details**, below the identity card. 2. Fill **Address**, **Phone** and **Email** as needed. 3. Select this card's **Save**. The saved-details notification confirms the update. **Address** allows up to 300 characters, **Phone** up to 40, and **Email** up to 254 with a valid email format. These fields can be left empty. An invalid entry is highlighted with a message beside that field. The two cards save independently. Saving contact details does not save unfinished edits in **Business identity**, or vice versa. ## If something goes wrong - The fields are read-only: only an owner or admin can edit them. Ask someone with that role to update the business information. - **Save** is disabled in the identity card: check that the business name is not blank and the knowledge field is within 20,000 characters. Also wait for an in-progress save. - The logo preview disappears or the app says the logo was not saved: choose the image again, then save. Do not assume a temporary preview is the stored logo. - A load error appears: select **Retry**. Avoid replacing existing details based on a failed load. - A save error appears: keep your text, check the connection and try the affected card again. Wait for the success message. ## Related pages - [Settings](https://docs.lead-knight.com/en/settings/overview/). - [Assistant guide](https://docs.lead-knight.com/en/assistant/overview/), including memory and writing style. - [Create a campaign with AI](https://docs.lead-knight.com/en/campaigns/create-with-ai/). - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/). ## Tell the AI about your business [Tell the AI about your business](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P5/nadlanite-en-7b1ce8f14694.mp4) 1. Your office’s details are in Settings. Scroll down to Business identity. 2. Here are your business name, industry, goals and office size. 3. Under What the AI should know, add the facts that make your office different. 4. Click Save. 5. AI writers use this knowledge whenever Business info is selected. --- # Set your workspace time zone Check and change the workspace time zone used to resolve scheduled campaign times. Canonical: https://docs.lead-knight.com/en/settings/time-zone/ ## What this changes The workspace **Time zone** determines how scheduled campaign times are resolved. It is separate from your interface language and from the time zone detected in your browser. Read the workspace value before planning a publication for a particular local hour. ## Before you start Check the current workspace and the local time zone you intend to use. This setting belongs to the workspace; it is not just a display preference for the current browser. If you are investigating a specific publication time, keep the relevant campaign's schedule available so you can compare it after the change. Changing the zone is not the same as editing an individual scheduled post. ## Choose a time zone 1. Open **Settings**. 2. Scroll to **Advanced** and locate **Time zone**. The card shows **Workspace time zone** and its current value. 3. Compare it with **Browser time zone:** below. The browser value is a reference, not a confirmation that it has been saved for the workspace. 4. Select **Change**. A searchable **Workspace time zone** selector appears. 5. Search for and choose the required zone, such as `Asia/Jerusalem`. The selector uses time-zone identifiers rather than a manually typed UTC offset. 6. The picker closes and the new value is saved automatically. Wait for saving to finish and check for an error or an unsaved-setting notice. 7. Open **Scheduled content** and the relevant campaign to check the dates and times you intend to use before publishing. There is no separate **Save** button on this card. **Cancel** closes the open selector without making a new choice. ## What the displayed values mean | Display | Meaning | | --- | --- | | **Workspace time zone** | The zone currently shown for workspace scheduling. | | **Browser time zone:** | The zone detected on this device. It can differ from the workspace zone. | | **Time-zone changes are not saved yet.** | The setting is not persisted. Do not treat the displayed choice as a successfully stored workspace setting. | When the time-zone service is unavailable, the card may display an inferred browser zone with the unsaved notice. That is not evidence that scheduling has adopted the browser zone. ## If something goes wrong - The card fails to load: select **Retry**. Do not guess the workspace zone from your computer clock. - A save error appears: the card rolls back to the previous value. Check the connection, select **Change** and try again. - The picker closes immediately after a selection: this is expected; selection starts saving automatically. - **Change** is temporarily disabled: wait for the current save to finish. - The unsaved notice remains: the workspace setting was not confirmed as persisted. Do not rely on it for an important scheduled publication; resolve the unavailable setting first. - A post appears at an unexpected time: compare the workspace zone, the campaign's actual schedule and the calendar view. Adjust the intended campaign schedule rather than repeatedly changing the workspace zone as a workaround. ## Related pages - [Settings](https://docs.lead-knight.com/en/settings/overview/). - [Scheduled content](https://docs.lead-knight.com/en/calendar/overview/). - [Campaign scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/). ## Set your workspace time zone [Set your workspace time zone](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P6/nadlanite-en-df3745276d77.mp4) 1. Scheduled posts go out by your workspace time zone. In Settings, scroll down to Time zone. 2. Click Change. 3. Open the list and search for your city. 4. Pick your time zone. It saves right away. 5. Scheduled campaigns now publish at times in this time zone. --- # Sign-in methods and notifications Check how you sign in, set or change a password, and choose email or WhatsApp delivery for your notifications. Canonical: https://docs.lead-knight.com/en/settings/sign-in-and-notifications/ ## What this is for Under **Settings** → **Account preferences**, **Sign-in methods** shows your signed-in email and lets you add or change a password. If Google is linked, the card shows **Google — connected**. Adding a password does not remove that Google sign-in method. The separate **Notifications** card controls additional delivery of CRM bell notifications by email and WhatsApp. It does not create a WhatsApp marketing campaign or send a message to your customers. ## Before you start - Use your own signed-in account. The email shown in **Sign-in methods** is the account whose password you will change. - Have access to that email inbox. A security confirmation may be required. - If your account uses an authenticator app, keep it available for the requested verification. - WhatsApp notifications need both an available WhatsApp notification service and a paired WhatsApp account. ## Set or change a password 1. Open **Settings** → **Account preferences** → **Sign-in methods**. Check the email address shown. 2. Select **Set or change password**. The form repeats **Setting a password for** and the target email. 3. Enter **New password**, using 8–200 characters with an uppercase letter, a lowercase letter and a number. 4. Enter the same value in **Confirm password**. 5. Select **Save password**. If no further verification is needed, the card returns to its normal view and confirms that the password was saved for that email. 6. If **For your security, confirm it’s you** appears, select **Email me a code**. After the email arrives, enter its six-digit **Confirmation code** and select **Save password** again. 7. If asked for **Authenticator app code**, enter the current six-digit code from your authenticator app and save again. The saved message explains that you can sign in with the displayed email and the new password. If Google is connected, it also remains an option. **Cancel** closes the password editor without submitting a new password. ## Security confirmations and recovery - **Send a new code** requests a replacement email code. Wait while the retry countdown is shown; repeated clicks do not bypass it. - **That code has expired — send a new one.** means the old code cannot finish the change. Request a fresh one and use the new email. - If the signed-in account changes while editing, the form stops the change and offers **Sign in again**. Check the account before starting again. - These controls are for an account you can already access. For a forgotten password, use the sign-in recovery flow described in [Your account](https://docs.lead-knight.com/en/account/overview/). ## Choose notification delivery 1. Stay under **Account preferences** and find **Notifications**. 2. Turn on **Email notifications** to receive bell notifications by email as well. Turning it off leaves the in-app notification channel. 3. Check **WhatsApp notifications**. When available and paired, turn it on to receive short WhatsApp notifications with action buttons. 4. If WhatsApp is available but not connected, select **Connect WhatsApp**. This opens **Connections**; complete the assistant WhatsApp connection there, then return to settings. 5. Wait for each change to finish saving before changing another switch. No separate save button is needed. The two notification switches are independent. A disabled switch with **Email is not available right now** or **WhatsApp isn't available right now** indicates service availability, not that clicking elsewhere has enabled delivery. For assistant-initiated meeting reminders, idle-contact alerts, morning briefings and quiet hours, use **WhatsApp messages from your assistant** under **Assistant** instead. Those controls are separate from the notification-delivery card. ## If something goes wrong - Sign-in methods fail to load: select **Retry**. If needed, **Sign out and try again** signs out locally so you can sign in again; do not use it while depending on an unsaved password form. - Passwords do not match: re-enter both values identically and follow the displayed character requirements. - An email code does not arrive: check the displayed target address and spam folder; use the resend control after its countdown. - A save fails: the app has not confirmed the password change. Check the connection and retry; do not assume the new password is active. - WhatsApp notifications cannot be enabled: check the pairing and service availability. Follow **Connect WhatsApp** only if offered. - A notification change fails: the switch returns to its previous value and shows a save error. Try again after checking the connection. ## Related pages - [Settings](https://docs.lead-knight.com/en/settings/overview/). - [Your account](https://docs.lead-knight.com/en/account/overview/). - [Connections](https://docs.lead-knight.com/en/channels/overview/). - [AI assistant](https://docs.lead-knight.com/en/assistant/overview/). ## Sign-in methods and notifications [Sign-in methods and notifications](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P7/nadlanite-en-ed9ca67d4869.mp4) 1. Your sign-in and notification choices are in Settings. 2. Sign-in methods shows the email and accounts you sign in with, like Google. 3. To also sign in with a password, click Set or change password. 4. Notifications decide where alerts reach you, besides the bell. 5. Turn email notifications off if you only want them in the app. 6. WhatsApp alerts need a connected WhatsApp number first. --- # Team and workspaces Understand memberships, roles and seats, switch workspaces, invite colleagues and manage requests to join. Canonical: https://docs.lead-knight.com/en/team/overview/ ## Your team at a glance Open **Team** to see **Members**, their roles and seat status in the current workspace. Your personal account can belong to several workspaces; membership and permission in one do not automatically apply to another. Nadlanite presents the workspace as an office. | Role | How the interface describes it | |---|---| | **Owner** | Owns the workspace and can initiate ownership transfer. | | **Admin** | Manages the team and billing, and publishes. | | **Member** | Prepares and publishes posts from their own accounts. | | **Viewer** | Sees workspace content and does not publish. | Permissions for specific actions still depend on the action and your seat. An admin is not the owner, and managing team billing does not mean every bill is personally theirs. ## Guides in this area - [Switch or create a workspace](https://docs.lead-knight.com/en/team/workspaces/): find your current membership, use another workspace, or start setup for a new one. - [Invite colleagues and accept invitations](https://docs.lead-knight.com/en/team/invitations/): email invitations, invitation links, correct account and expiry. - [Join with a workspace code](https://docs.lead-knight.com/en/team/join-requests/): request access and approve or decline applicants. - [Manage roles, seats and departures](https://docs.lead-knight.com/en/team/roles-and-seats/): understand approval, payer and ownership constraints. ## Read seat status separately from role A person's role says what they may do; seat status says whether their subscription access is ready. Rows can show **Active**, **Payment issue**, **Frozen**, **Needs to set up billing** or **Waiting for sponsor**, and a trial end where applicable. A **Viewer** has a seat too; viewing is not an unlimited free membership. With self-pay, people set up their own seats. With sponsored billing, the sponsor pays and sets them up. A request or invitation alone does not guarantee an active seat. See [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) for plan confirmations and payment status. ## Who can manage the team Owners and admins can invite people and review join requests. Removal and role changes have additional restrictions. If a management control is missing, check your role instead of assuming the page failed. Every member can use the Team page to understand the team and their seat even when a billing gate prevents other work. ## Related areas - [Getting started](https://docs.lead-knight.com/en/getting-started/overview/) - [Onboarding after joining](https://docs.lead-knight.com/en/getting-started/onboarding/) - [Workspace settings](https://docs.lead-knight.com/en/settings/overview/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) --- # Switch or create a workspace Select an existing membership, request to join another workspace, or start a separate workspace without replacing the current one. Canonical: https://docs.lead-knight.com/en/team/workspaces/ ## What this is for The workspace switcher lists the workspaces you belong to and your role in each. Switching changes where you work, not who you are signed in as. A workspace's content, connections, role and seat access can differ from another's. ## Before you start Save any work using the current page's own controls before leaving it. Make sure the workspace name you want is in your membership list; otherwise request to join it or accept an invitation. ## Switch to an existing workspace 1. On desktop, open **Switch workspace** in the sidebar. On a phone, choose **More**, then the workspace switcher at the bottom of the panel. 1. Review the listed names and roles. A check identifies **Current workspace**. **Setting up** means that workspace has not finished opening. 1. Choose the other workspace's name. The app switches its current workspace. If your membership still needs setup or a seat, the relevant flow explains what to complete. 1. Check the workspace name and your role before editing or publishing. The small identity line can also show your seat's plan here. ## Create a separate workspace 1. Open the switcher and choose **Create a workspace**, or **Create an office** in Nadlanite. 1. The onboarding wizard opens for a new workspace. The existing workspace remains as it is; a new name and setup are required. 1. Complete [onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/). The workspace step creates the new workspace; merely opening the new-setup link does not create it. To join an existing team instead, choose **Join a workspace** and follow [Join requests](https://docs.lead-knight.com/en/team/join-requests/). Do not create a duplicate workspace to access someone else's data. ## Discarding an unfinished workspace Only an owner may see **Discard** for a workspace that was never opened and has not completed their onboarding there. The confirmation warns that discarding removes it and everything prepared in it and cannot be undone. A workspace with a seat or bill is not eligible for this shortcut. Cancel if you are unsure; this is not a way to archive an active office or cancel its subscription. ## If something goes wrong | Symptom | Next step | |---|---| | The workspace is not listed | Use its invitation or request to join; knowing its name alone does not grant membership. | | The wrong data appears | Check the selected workspace before making changes. | | **Setting up** appears | Open that workspace and complete its remaining setup. | | Discard is refused | Its state may have changed or it is no longer eligible. Do not retry it as a subscription cancellation. | | A discarded workspace needs cleanup | If the dialog offers **Finish disconnecting**, use that action; the workspace has already been discarded. | ## Related pages - [Team overview](https://docs.lead-knight.com/en/team/overview/) - [Join with a code](https://docs.lead-knight.com/en/team/join-requests/) - [Invitations](https://docs.lead-knight.com/en/team/invitations/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) ## Switch between workspaces [Switch between workspaces](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/C4/leadknight-en-84cb51e5a2b8.mp4) 1. Your current workspace is shown at the bottom of the menu. 2. Click it to see all your workspaces. 3. You can also join a teammate’s workspace with a code, 4. or create a new one. 5. Pick a workspace to switch to it. 6. Everything now shows that workspace: its content, contacts and team. --- # Invite colleagues and accept an invitation Invite a person by email or link, check the role and payer, and accept using the email address the invitation was sent to. Canonical: https://docs.lead-knight.com/en/team/invitations/ ## Before you start To invite someone, be an owner or admin of the correct workspace. Know the person's email and intended role. Check whether people pay for their own seats or a workspace sponsor pays; inviting someone is not the same as completing their seat setup. ## Send an invitation 1. Open **Team** and choose **Invite**. The invitation form opens. 1. Enter **Email** and select **Role**. The choices describe **Admin**, **Member** and **Viewer** permissions. Choose the least access the person needs. 1. If sponsored plan choices appear, review them and the joining/payment explanation. The UI says joining charges the sponsor nothing; if a free trial was already used, the first charge is separately quoted and confirmed later through **Assign plan**. 1. Choose **Send invitation email** to send it, or **Copy invitation link** to copy the link for sharing with the intended recipient. 1. Review **Pending invitations**. **Copy link** refreshes a pending link and warns that the earlier link stops working. **Revoke** cancels an invitation you no longer want accepted. ## Accept an invitation 1. Open the invitation link. Its preview identifies the workspace, inviter, role and validity date, and explains who pays for the seat. The invited address can be partly masked before sign-in. 1. Create an account or sign in with that invited email address. The authentication flow returns to the invitation. 1. If signed in with another address, choose **Sign out and continue with the invited address**. Do not accept a colleague's invitation from your own unrelated account. 1. Choose **Accept invitation**. The app remembers the workspace and opens the applicable onboarding path. 1. Complete your personal setup and seat requirements. If already a member, use **Open the app** or the workspace-opening action shown rather than accepting again. ## Rules and options Invitations are address-specific and time-limited; use the preview's validity date. Only one pending invitation for the same address can exist in a workspace. Sending invitations is rate-limited. An expired, refreshed or revoked link must be replaced by an authorized team member, not repaired by editing the URL. Admins manage the team and billing and can publish. Members prepare and publish from their own accounts. Viewers see content but do not publish. A role does not override seat restrictions or grant access to every colleague's publishing identity. ## If something goes wrong | Symptom | What to do | |---|---| | Wrong signed-in email | Sign out through the invitation's action and use the invited address. | | The link expired or stopped working | Ask the inviter for the latest link. A refreshed link invalidates the earlier one. | | An invitation is already pending | Manage the existing pending invitation rather than repeatedly creating another. | | Invitation sending is limited | Wait before trying again and avoid repeated invitations to the same address. | | Joined but cannot continue | Finish onboarding and seat setup, or wait for the sponsor named by the page. | | Invite controls are missing | Check your role and selected workspace. Owners/admins manage invitations. | ## Related pages - [Team overview](https://docs.lead-knight.com/en/team/overview/) - [Roles and seats](https://docs.lead-knight.com/en/team/roles-and-seats/) - [Join by code](https://docs.lead-knight.com/en/team/join-requests/) - [Create an account](https://docs.lead-knight.com/en/getting-started/create-account/) --- # Join a workspace with a code Send a membership request using a workspace code, track its status, and understand how team leaders approve requests. Canonical: https://docs.lead-knight.com/en/team/join-requests/ ## What a code does A workspace code lets you request membership. It does not immediately add you, activate your seat, or make you an administrator. An invitation sent to your email is a separate route; see [Invitations](https://docs.lead-knight.com/en/team/invitations/). ## Before you start Sign in to your own account and get the current code from the workspace owner or an admin. Check which office or workspace you intend to join. During first-time Nadlanite setup, the office step can also offer joining by code; [onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/) explains that path. ## Send and track your request 1. Open the join page, or choose **Join a workspace** from the workspace switcher. 1. Enter **Workspace code** and choose **Send request**. A successful submission shows **Request sent — waiting for approval**. 1. Review your requests and status: **Waiting for approval**, **Approved**, **Declined** or **Canceled**. The request's workspace name and date help identify it. 1. While pending, wait for the team's decision. If the wrong workspace was requested, use the cancellation option provided rather than sending more requests. 1. Once approved, choose the action labelled **Continue to** followed by the workspace name. The app opens onboarding for that membership; complete the personal and seat steps that apply to your role. ## For owners and admins 1. In **Team**, find **Join code**. Use **Copy** to share it with the intended person. 1. To replace it, choose **Rotate code**. The old code stops working immediately; send the new one to people who still need to apply. 1. Review **Join requests** and verify who is asking to join. 1. Select the appropriate role and any sponsored-plan choices offered, then choose **Approve** or **Decline**. 1. If a sponsored member still needs a paid plan, use **Assign plan** when offered and review the quoted charge before confirming. Joining itself does not charge the sponsor's card. ## Rules and scope Only owners and admins can manage the join code and decide requests. Approval grants the selected membership, not unrestricted access to other workspaces or colleagues' accounts. Seat access may still need setup. Code rotation affects use of the old code; it is not an action to remove existing members. ## If something goes wrong | Symptom | Cause and next step | |---|---| | Code rejected | Check for typing errors and ask for the latest code; the office may have rotated it. | | Request remains pending | The team has not approved it. Contact an owner/admin instead of creating a duplicate workspace. | | Request declined | You were not added. Clarify with the team before trying again. | | Approved but no access | Use the continue action and finish the required onboarding and seat steps. | | Join code controls missing | You need an owner/admin role in that workspace. | ## Related pages - [Team overview](https://docs.lead-knight.com/en/team/overview/) - [Switch workspaces](https://docs.lead-knight.com/en/team/workspaces/) - [Roles and seats](https://docs.lead-knight.com/en/team/roles-and-seats/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) --- # Manage roles, seats and departures Review member permissions, handle priced role changes and sponsored seats, and understand removal, leaving and ownership transfer. Canonical: https://docs.lead-knight.com/en/team/roles-and-seats/ ## Before you start Open the correct workspace's **Team** page and check your role. Each member has an individual seat. A **Viewer** seat is half the plan price; changing between viewer and a publishing role can affect billing and require more than one person's approval. ## Change a role 1. Find the person in **Members** and review both their current role and seat status. 1. Choose **Change role** where permitted and select the intended role. 1. If shown, review **New monthly total** and the amount charged now for the rest of the billing period. If the price cannot be loaded, do not confirm using an assumed amount. 1. Confirm **Change role**. The result may say **Role changed** or **Waiting for the other approver**. 1. For a pending priced change, review **Role change requests**. The appropriate approver chooses **Approve** or **Decline**; the requester can use **Withdraw** where offered. A priced role change can require both leadership and payer approval. The owner's role is not changed through this ordinary role selector. The screen only offers changes authorized for the current person and member. ## Set up a sponsored member's seat 1. As the sponsor, find the waiting member and choose **Assign plan** when offered. 1. Select **Plan** and **Term**. 1. Read the charge to your card today, regular monthly payment including VAT and effective date. 1. Choose **Assign** only after reviewing the quote. A changed quote must be reviewed again. The seat status then reflects the server's result, not merely the fact that the dialog closed. A sponsored member cannot activate the sponsor's card on their own. If you are the member, wait for the sponsor and use the check-again action in your setup flow. See [Billing](https://docs.lead-knight.com/en/billing/overview/). ## Remove a member or leave yourself - Owners may remove other eligible members. Admins may remove members and viewers, not the owner or another admin. The sponsor cannot be removed through this action. - Use **Remove** beside the eligible person and read the confirmation. Removal is not the same as canceling someone's personal billing; review any remaining seat and billing obligations separately. - To leave your own membership, use **Leave workspace** rather than removing yourself. Its confirmation warns that access is lost immediately. - The owner and sponsor cannot leave through the ordinary leave action. Resolve ownership or sponsorship first using the appropriate controls. ## Transfer ownership The owner uses **Transfer ownership**, selects an admin through **Choose an admin**, and chooses **Start transfer**. The recipient sees the pending transfer and accepts or declines. Starting it is not the same as the recipient accepting ownership. ## Paid-campaign permission is separate Where shown, the sponsor's **Paid campaigns** controls decide whether a member may run campaigns whose management fee is billed to that sponsor. Read the consequence before allowing or revoking. Revoking prevents new starts, resumes and budget increases billed to the sponsor; it does not stop campaigns already running. ## If something goes wrong - A control is absent: check role, target member and whether the person is the owner or sponsor. - A role change is pending: another required approver has not accepted; do not assume it is active. - Price unavailable: reload the page and review a fresh quote before confirmation. - A member is frozen despite the expected role: seat access is a billing state, not a role change. Ask the payer to inspect billing. - Leaving is blocked: owners and sponsors need to resolve their responsibilities first. ## Related pages - [Team overview](https://docs.lead-knight.com/en/team/overview/) - [Invitations](https://docs.lead-knight.com/en/team/invitations/) - [Workspace switching](https://docs.lead-knight.com/en/team/workspaces/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) --- # Plans and billing Understand personal seats, plan terms, trial eligibility, secure card setup, invoices and assistant allowances. Canonical: https://docs.lead-knight.com/en/billing/overview/ ## Where to find billing Open the account avatar and choose **My billing**. The page heading is **Billing**. This is your personal billing view across the seats you pay for, not just the current workspace. **Your plan**, **Transaction history**, **Billing information** and **Payment method** describe your own arrangements. **Team seats** provides workspace controls when your role or sponsorship allows them. Billing and purchase availability can differ between workspaces. If purchase is not available for yours, follow the on-screen message; do not assume that opening the billing page means checkout is enabled for everyone. ## Guides in this area - [Choose a plan and start a trial](https://docs.lead-knight.com/en/billing/choose-plan/): what is included, monthly pricing, commitments, eligibility and confirmation. - [Complete secure card setup](https://docs.lead-knight.com/en/billing/secure-checkout/): new-card popup, returning to the original tab and uncertain outcomes. - [Manage plans, cards and invoices](https://docs.lead-knight.com/en/billing/manage-billing/): billing contact, changes, cancellation and payment status. - [Understand AI assistant allowances](https://docs.lead-knight.com/en/billing/assistant-allowance/): daily and short-term limits, reset time and usage notices. ## Seats and who pays Each person has a seat in each workspace they use. A role and a seat are different: the role controls permissions, while the seat's state controls subscription access. Viewer seats are half the plan price. With self-pay you set up your own seat; with sponsored billing a sponsor pays and sets it up. Joining a workspace or accepting an invitation is not, by itself, confirmation of a charge. A paid action shows its price and consequences before confirmation. A sponsor may need **Assign plan** on **Team** after a member joins. See [Team](https://docs.lead-knight.com/en/team/overview/). ## Trials, terms and actual amounts The public sign-up screen advertises ten free days. The plan/seat flow shows actual eligibility and duration, requires a card for the trial, and explains that no charge is made today during the trial. Cancel before it ends to avoid the first charge. If your free trial has already been used, the dialog shows the amount due today instead. Monthly, quarterly and yearly choices are billed monthly. Quarterly and yearly choices have a commitment; canceling renewal does not cancel payments remaining within that commitment. Always use the current quote, including VAT and the effective date, rather than a price remembered from a video or this guide. ## Reading status **Trial**, **Active**, **Payment issue**, **Frozen**, **Ended**, **Payment being confirmed**, **Needs a card** and **Not set up** are different states. A completed card-entry window is not proof of an active seat or paid invoice. Return to the original app tab and read the result. If a payment is being confirmed, follow that message rather than paying again. Paid-campaign fees, when shown, are separate from seat charges. The billing interface describes 10% of actual ad spend plus VAT and may show an estimate for the current month; the final amount uses the platform's final figures. See [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) for campaign operations. ## Related pages - [Getting started](https://docs.lead-knight.com/en/getting-started/overview/) - [Your account](https://docs.lead-knight.com/en/account/overview/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) ## Choose your plan and start the free trial [Choose your plan and start the free trial](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P8/nadlanite-en-eca015747cea.mp4) 1. Before your seat starts, you choose a plan. 2. Every plan starts with ten days free. Nothing is charged today, and you can cancel during the trial. 3. Monthly has no commitment. 4. Quarterly commits for three months at a lower monthly price. 5. Yearly has the lowest monthly price. 6. All plans include the same features. 7. Open the questions below for answers about the trial, cancelling, and invoices. 8. When you are ready, click Start free on the plan you want, and add your card on the secure payment page. --- # Choose a plan and start your trial Compare what is included, understand monthly charges and commitments, and confirm the exact seat quote before activation. Canonical: https://docs.lead-knight.com/en/billing/choose-plan/ ## Before you start Know which workspace and member the seat is for and who pays. A viewer seat has a different price from a full seat. Billing availability and trial eligibility are determined by the current account and workspace; use the quote displayed rather than assuming a new trial for each new workspace. ## What the plan cards include The plan screen's **Everything included in every plan** list shows: - **AI-assisted post text and images**. - **Facebook group posting from your own profile**. - **Publishing to connected social accounts**. - **Campaigns and scheduling calendar**. - **Contacts**. - **Team roles and permissions**. The connected-account allowance comes from the selected plan and is displayed on the screen; do not assume the same count for every plan. The real-estate edition adds **Property details to advertising copy**. Included capabilities still require applicable connections, permissions and feature availability. Assistant use has allowances; it is not unlimited. ## Select and review 1. Open the available plan-selection action from billing or the setup flow. You see the current catalog's plans and terms. 1. Choose **Monthly**, **Quarterly** or **Yearly** as offered. Prices are per month plus VAT. Monthly has no minimum commitment; quarterly and yearly mean three or twelve monthly payments, not one payment for the entire term. 1. Select the plan and continue to its payment/seat review. Check the workspace, payer and role before proceeding. 1. Read **Charged today**, **Regular monthly payment (including VAT)**, **Next billing date** and **Payment method**. Read the commitment and renewal explanation too. 1. If a trial is available, review its actual duration and the no-charge-today explanation. A card is required. If the trial has already been used, **Activate your seat** shows the charge due today. 1. Accept the displayed recurring-payment and terms consent where required. If an applicable discount-code field is offered, apply the code and review the updated first-payment quote; an invalid or ineligible code is not applied. 1. Choose the action that matches your intent. **Start trial** or **Activate seat** opens seat access without publishing. **Start trial & keep draft** or **Activate & keep draft** preserves a draft. **Start trial & continue to publish** or **Activate & continue to publish** continues the publishing flow; queued is not delivered. An AI-creation flow can start background content creation after activation. 1. If using a new card, complete [secure checkout](https://docs.lead-knight.com/en/billing/secure-checkout/). Read the activation result in the original app tab. ## Trial end and renewal During an eligible trial, nothing is charged today. Cancel before the trial ends to avoid its first charge. Otherwise the selected plan starts automatically at the monthly price plus VAT; a quarterly or yearly commitment begins with it. Canceling renewal during a commitment does not remove the remaining payments. Review the current date and cancellation terms shown for your seat. A sponsored seat instead tells you the sponsor sets it up. Wait for that setup; do not enter your own card unless deliberately switching to a self-pay arrangement through its proper flow. ## If something goes wrong - No purchase available: follow the availability message; do not assume billing is enabled for every workspace. - Price cannot load: retry loading; no guessed price should be confirmed. - Quote or consent changed: review the new amount and terms and agree again. - Trial unavailable: the screen can explain that it was already used; review the actual charge due today. - Discount refused: check whether it is expired, for new customers, already used or your own code. - Sponsor still pending: ask the sponsor to finish setup or assign the plan. ## Related pages - [Billing overview](https://docs.lead-knight.com/en/billing/overview/) - [Secure card setup](https://docs.lead-knight.com/en/billing/secure-checkout/) - [Manage renewal and invoices](https://docs.lead-knight.com/en/billing/manage-billing/) - [AI assistant allowances](https://docs.lead-knight.com/en/billing/assistant-allowance/) ## Choose your plan and start the free trial [Choose your plan and start the free trial](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P8/nadlanite-en-eca015747cea.mp4) 1. Before your seat starts, you choose a plan. 2. Every plan starts with ten days free. Nothing is charged today, and you can cancel during the trial. 3. Monthly has no commitment. 4. Quarterly commits for three months at a lower monthly price. 5. Yearly has the lowest monthly price. 6. All plans include the same features. 7. Open the questions below for answers about the trial, cancelling, and invoices. 8. When you are ready, click Start free on the plan you want, and add your card on the secure payment page. --- # Complete secure card setup Enter a card on the payment provider's page, return to the original app tab, and distinguish a confirmed result from a pending payment. Canonical: https://docs.lead-knight.com/en/billing/secure-checkout/ ## Before you start Keep the original app tab open. Review the plan, charge today, recurring amount, VAT, next billing date and commitment before confirming. For card addition or replacement, verify the billing contact too. Card entry happens on the payment provider's secure hosted page, not inside a chat or a help form. ## Enter and verify the card 1. In the plan or card dialog, select the payment method and provide **Name on card** and **Billing email** where requested. Invoices use this billing contact. 1. Read and accept the applicable payment consent. Choose the confirmation action. A new card opens a secure card window; an already saved method may not require entering a card again. 1. Complete the provider's card page. The original app tab shows **Finish on the secure card page.** while waiting. 1. At the return page you may see **You can close this window** and **Finishing up in the original tab.** The window tries to close itself. If it remains open, close that return window yourself. 1. Return to the original app tab and read its actual result. That tab checks the provider outcome and displays the seat or card result. The return page itself does not prove payment success. 1. If the original flow is waiting, use **Check again** when offered. If told that the seat is active and the first payment is being confirmed, do not pay again. ## What different outcomes mean | Message or state | What to do | |---|---| | Card was saved or replaced | The card action completed. A plan activation has its own result; do not assume all pending seats started. | | Seat is active with a charge amount | Read the amount actually charged and inspect billing if needed. | | Trial has started | Review the trial end/next billing date. A free trial still has its selected renewal terms. | | First payment declined after card save | Follow the message to try another card; saving a card was not a successful payment. | | Provider answer not received | If you finished entering the card, check **My billing** in a few minutes. Do not repeatedly initiate payments. | | Payment being confirmed | Wait for confirmation and follow the stated instructions rather than paying again. | | Card page expired | Restart through the app's offered action to obtain a current secure page. | | Card window closed before saving | Reopen through the original app flow if you still want to continue. | ## Browser and reload options If the browser blocks the popup, allow popups for the app and choose **Open the secure card page** where offered. Opening a random old provider link is not a substitute for the current checkout. After a reload, the app may resume waiting for the card page opened earlier. **Start over** is offered for flows that allow a fresh attempt. Read any pending-payment message first: a network error or closed tab does not prove that no payment occurred. ## If something goes wrong - Secure page never opened: check popup blocking and use the provided open action. - Return window closed quickly: this is expected; read the original tab. - Payment status cannot be checked: let the retry/check flow recover, then consult billing rather than resubmitting blindly. - Purchase is unavailable: checkout may not be enabled for this workspace; use the displayed guidance. - An unresolved outcome persists: contact support with the displayed state and time, never with your full card number or security code. ## Related pages - [Choose a plan](https://docs.lead-knight.com/en/billing/choose-plan/) - [Manage billing](https://docs.lead-knight.com/en/billing/manage-billing/) - [Billing overview](https://docs.lead-knight.com/en/billing/overview/) ## Choose your plan and start the free trial [Choose your plan and start the free trial](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P8/nadlanite-en-eca015747cea.mp4) 1. Before your seat starts, you choose a plan. 2. Every plan starts with ten days free. Nothing is charged today, and you can cancel during the trial. 3. Monthly has no commitment. 4. Quarterly commits for three months at a lower monthly price. 5. Yearly has the lowest monthly price. 6. All plans include the same features. 7. Open the questions below for answers about the trial, cancelling, and invoices. 8. When you are ready, click Start free on the plan you want, and add your card on the secure payment page. --- # Manage your plan, card and invoices Read personal billing, update a saved card and contact details, review plan changes, and cancel renewal without confusing it with immediate cancellation. Canonical: https://docs.lead-knight.com/en/billing/manage-billing/ ## Before you start Open **My billing** from the account menu. The page title is **Billing**. Check the workspace name on each seat: this personal page can show more than one workspace. If another person sponsors your seat, their payment responsibilities are not the same as your personal card details. ## Read your plan and transactions 1. Under **Your plan**, review the workspace, plan/term, monthly amount, status and renewal dates. A pending change has its own effective date. 1. Under **Transaction history**, review bill amounts and states. **Paid** differs from **Due**, **Payment failed — retrying**, **Declined** or **Being confirmed**. 1. Use **View invoice** where offered to open the tax invoice/receipt. The plan screen states that a tax invoice/receipt is also emailed for every charge to the billing email. 1. If a paid-campaign fee section appears, distinguish its month-to-date estimate from final bills. The estimate says it is charged on the third of the following month and uses the platform's final figures. ## Add or replace a card 1. In **Payment method**, choose **Add card** or **Replace card**. The page shows only the saved card's masked ending, not the full number. 1. Review **Name on card** and **Billing email** in the card flow. **Billing information** explains that replacing the card is also how you update those contact fields. 1. Confirm the consent and finish [secure card setup](https://docs.lead-knight.com/en/billing/secure-checkout/). 1. Return to the original tab and check the saved/replaced result. A card change is not proof that an unresolved past payment has been settled; read the bill state. ## Change plan or commitment 1. Choose **Change plan** beside the correct seat. 1. Review the available new plan or term and the price shown. 1. Read whether it takes effect immediately or at the end of the existing commitment, and whether a charge, credit or new commitment applies. 1. Confirm only after reviewing those details. Check the result for the charged amount or scheduled date. The interface distinguishes an immediate upgrade charge, a longer commitment with applicable next-bill credit, shortening at the end of the current commitment, and trial changes with no charge during the trial. The exact outcome depends on your seat and chosen change; do not assume every change happens now or costs nothing. ## Cancel renewal 1. Find **Cancel plan** for the correct workspace's seat. 1. Read the confirmation asking to cancel renewal at the end of the current commitment. 1. Confirm only if that is what you intend. The plan remains active until the end of its term and payments for a committed period continue until it ends. 1. Check the displayed end or pending-cancellation information. During a trial, cancel before the trial ends to avoid its first charge. Canceling renewal is not an immediate refund, removing a team member or deleting the workspace. Leaving a workspace likewise does not erase an existing payment commitment. ## Team billing and sponsorship Authorized owners/admins and sponsors can see **Team seats**. Read each change's payer, amounts and dates. Switching to sponsored billing requires the designated sponsor's confirmation. Where a workspace switches to self-pay, **Workspaces switched to self-pay** can ask you to **Set up my billing** to keep your seat. Do not assume someone else's card will continue paying after a payer change. ## If something goes wrong - No personally billed plan: the page may correctly say you have none; your seat may be sponsored. - Payment being confirmed: follow the message and do not pay again just to clear it. - Frozen seat or payment issue: the responsible payer should inspect the card and bill state. - A quote changed: read the updated amount and confirm again only if you agree. - An invoice cannot open: retry from the current billing page rather than relying on an old document link. - Billing action unavailable: check role, payer, current payment processing and workspace purchase availability. ## Related pages - [Billing overview](https://docs.lead-knight.com/en/billing/overview/) - [Choose a plan](https://docs.lead-knight.com/en/billing/choose-plan/) - [Secure card setup](https://docs.lead-knight.com/en/billing/secure-checkout/) - [Team and roles](https://docs.lead-knight.com/en/team/overview/) ## Choose your plan and start the free trial [Choose your plan and start the free trial](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P8/nadlanite-en-eca015747cea.mp4) 1. Before your seat starts, you choose a plan. 2. Every plan starts with ten days free. Nothing is charged today, and you can cancel during the trial. 3. Monthly has no commitment. 4. Quarterly commits for three months at a lower monthly price. 5. Yearly has the lowest monthly price. 6. All plans include the same features. 7. Open the questions below for answers about the trial, cancelling, and invoices. 8. When you are ready, click Start free on the plan you want, and add your card on the secure payment page. --- # Understand AI assistant allowances Learn why the assistant has daily and short-term limits, when access returns, and how to read the usage-limit notice. Canonical: https://docs.lead-knight.com/en/billing/assistant-allowance/ ## Daily and short-term limits The assistant has both a daily allowance and a shorter rolling-window limit. The daily allowance resets at midnight in the workspace's local time zone, not necessarily your device's midnight. Interactive conversations also have a rolling three-hour limit: recent activity stops counting as it leaves that window. The allowance covers AI work and outbound assistant messages, so the number of requests you typed is not the whole usage measure. Long or involved work can use more allowance than a short exchange. Scheduled AI work and interactive chat do not use every allowance in exactly the same way. Exact quantities can depend on the plan's usage policy; this guide does not promise a fixed number of prompts or tokens. ## What the notice means When a limit is reached, the conversation can show **Assistant usage limit reached**. It identifies whether the daily or three-hour budget for AI work or outbound messages is responsible. If a reply is already being produced, the notice explains **The current reply can finish. New requests are paused.** That does not grant unlimited further actions. The notice gives the time you can send new requests again. If daily and rolling limits both apply, both must clear; reaching local midnight does not necessarily remove a still-active rolling limit. Use the displayed availability time. The usage panel appears for a reached limit. Do not rely on receiving an advance warning before every limit or on a permanent remaining-allowance meter. ## What to do when paused 1. Read the limiting category and availability time in the conversation. 1. Let a current reply finish. New requests stay paused while the applicable restriction remains. 1. After the displayed availability time, choose **Refresh usage** if needed. That action is disabled while a reply is streaming. 1. If availability is still being checked, refresh again later rather than repeatedly sending the same request. Refreshing checks the state; it does not buy more allowance or reset the day. Starting another conversation does not itself bypass the usage policy. A usage pause is not a subscription payment failure. ## Time zone and other notifications If the reset time seems wrong, check the workspace time zone in [Settings](https://docs.lead-knight.com/en/settings/overview/). Email and WhatsApp notification preferences are also there. CRM notifications and reminders have their own WhatsApp allowances; their delivery rules are not the same as sending another assistant-chat reply. ## If something seems wrong - A daily pause is still present after your phone's midnight: compare against the workspace's time zone and the availability time shown. - A short-term pause lasts beyond the oldest recent message: enough usage must leave the rolling window, not just one message. - The notice cannot refresh: check connectivity and use **Refresh usage** again when no reply is streaming. - A light-looking conversation used more than expected: AI work and outbound replies are counted, not just your incoming prompts. If the displayed restriction persists unexpectedly, ask support to investigate the actual usage. ## Related pages - [AI assistant](https://docs.lead-knight.com/en/assistant/overview/) - [Billing overview](https://docs.lead-knight.com/en/billing/overview/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) --- # Your account Manage your personal profile and sign-in methods, find account preferences, use the affiliate program and share feedback. Canonical: https://docs.lead-knight.com/en/account/overview/ ## Personal account or workspace? Your account is the person who signs in. A workspace is the team and content you are working with. You can belong to several workspaces, with a different role and seat in each. Changing your personal profile is not the same as changing an office logo, transferring ownership or switching the payer. Open the header avatar to find **My profile**, **My billing** and sign-out. On smaller screens, language and light/dark controls are in this menu too. ## Guides in this area - [Update your profile](https://docs.lead-knight.com/en/account/profile/): name, phone, gender, photo, bio and the real-estate broker-license field. - [Understand and manage sign-in methods](https://docs.lead-knight.com/en/account/sign-in-methods/): Google, email/password and identity confirmation. - [Join the affiliate program](https://docs.lead-knight.com/en/account/earn/): business details, customer discount, referral code and commission. - [Track affiliate payouts and documents](https://docs.lead-knight.com/en/account/affiliate-payouts/): held earnings, payout status and required documents where offered. - [Rate your experience and send feedback](https://docs.lead-knight.com/en/account/feedback/): the in-app rating request and optional follow-up offers. ## Preferences live in Settings Language, appearance and notification preferences are not edits to your profile photo or biography. For email and WhatsApp notification preferences, sign-in settings and other account preferences, see [Settings](https://docs.lead-knight.com/en/settings/overview/). The bell displays notifications; its presence does not mean every external delivery channel is connected or enabled. ## Your bills are personal too **My billing** can show seats you pay for across workspaces, including sponsored seats you fund. Updating **Phone** in your profile does not change the **Billing email** on a saved payment method. See [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) for card and billing-contact changes. ## Availability If you don't see **Earn** in the menu, it isn't enabled for your workspace yet. The affiliate page can also state that the program is not open or is closed to changes. The rating page only has a form when a rating request is available. Do not treat either an unavailable referral program or an empty rating page as an account-sign-in failure. ## Related pages - [Create an account](https://docs.lead-knight.com/en/getting-started/create-account/) - [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) --- # Update your personal profile Save your name, phone, gender, profile photo and bio, with an optional broker licence number in the real-estate edition. Canonical: https://docs.lead-knight.com/en/account/profile/ ## What the profile changes Your personal profile belongs to your account. It is distinct from the workspace's business identity and billing contact. You can edit personal details without renaming the office or changing its logo. ## Before you start Sign in to your own account and have the intended phone number and optional photo ready. If you are trying to update the business description or office logo, use [Settings](https://docs.lead-knight.com/en/settings/overview/) instead. ## Update the fields 1. Open the account avatar and choose **My profile**. The **Your profile** card loads the saved values. 1. Edit **Full name**. A nonempty name is required to enable **Save**; the field allows up to 200 characters. 1. Check **Phone**. You may leave it empty; if supplied, enter a valid number, such as an Israeli mobile number in local or international format. The number cannot already be used by another account. 1. Choose **Gender** using **Male** or **Female**. These are the choices the current form provides. 1. In Nadlanite, optionally fill **Broker licence number**. The field accepts 1–10 digits or can be left empty. 1. Choose **Your photo** to select an image. Review the preview. If a background-removal choice appears, choose whether to keep the original or use the processed image before upload. 1. Edit **About you** if wanted. The biography field allows up to 2,000 characters. 1. Choose **Save** and wait for **Profile saved.** A preview alone is not confirmation that the profile was saved. ## Photo options and limits The photo helps people recognize you. Use **Remove photo** where offered to remove the selected/saved photo, then save the profile. Upload errors or an unavailable file are shown explicitly. If an image could not be kept, choose it again rather than assuming the preview is stored. The profile form does not change your sign-in email or payment card. Manage sign-in methods through [Settings](https://docs.lead-knight.com/en/settings/overview/); manage the billing contact through [Billing](https://docs.lead-knight.com/en/billing/overview/). Notification preferences also live in Settings, not in the biography. ## If something goes wrong | Symptom | What to do | |---|---| | Profile cannot load | Check connectivity and choose **Retry**. | | Save is disabled | Enter a nonblank full name and wait for any current save to finish. | | Phone is invalid | Use a real valid phone number and correct its format. | | Phone is already used | Check whether it belongs to another account you own; resolve that account conflict instead of using someone else's number. | | Licence number refused | Use digits only, up to the stated length, or leave the optional field empty. | | Photo unavailable | Select the image again and save; a local preview is not a saved file. | | Save failed | Keep the desired values on screen, check the connection and retry saving. | ## Related pages - [Account overview](https://docs.lead-knight.com/en/account/overview/) - [Sign-in methods](https://docs.lead-knight.com/en/account/sign-in-methods/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) - [Billing](https://docs.lead-knight.com/en/billing/overview/) ## Update your profile [Update your profile](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P4/nadlanite-en-ce1b158555df.mp4) 1. Your personal details live in your profile. Open the account menu. 2. Choose My profile. 3. Your name and phone number can be added to the end of your posts. 4. Add your broker licence number, so posts can show it too. 5. Click Save. 6. Your profile is up to date. --- # Manage your sign-in methods Check the account email and Google connection and add or change an app password with the identity confirmation requested. Canonical: https://docs.lead-knight.com/en/account/sign-in-methods/ ## Available sign-in methods The app supports email/password and **Continue with Google**. Creating an account with Google does not mean an app password already exists. A Google-connected account can add a password for the same account; this does not change its Google password or disconnect Google. ## Before you start Sign in as the intended person. Have access to the account email and, if the account uses an authenticator, that app. The profile contact fields are not controls for changing your authentication identity. Detailed preference navigation is in [Settings](https://docs.lead-knight.com/en/settings/overview/). ## Add or change your password 1. Open **Settings**, then **Account preferences**. Find **Sign-in methods**. 1. Check the account email shown. **Google — connected** appears if the current account has that connection. 1. Choose **Set or change password**. The password form identifies the account it is changing. 1. Enter **New password** and **Confirm password**. Use 8–200 characters with an uppercase letter, a lowercase letter and a number. Both entries must match. 1. Choose **Save password**. If the app asks **For your security, confirm it’s you**, follow the confirmation flow rather than repeatedly resubmitting the password. 1. If offered, choose **Email me a code**, enter the **Confirmation code** from the email and continue. If the account uses two-step verification, enter the **Authenticator app code** requested instead. 1. Wait for the saved-password confirmation. It names the email you can use with the new password and also mentions Google when connected. ## Codes, identity and preferences Email and authenticator codes are six digits. Use the latest email code; **Send a new code** is available when appropriate. Respect any cooldown shown. An expired code is not a reason to create another app account. If the signed-in account changes during editing, the form stops the operation and asks you to sign in again. This prevents saving a password against the wrong identity. Support sessions do not expose this password editor. For a forgotten password when signed out, use **Forgot password?** on the login page and follow the reset email. See [Create an account](https://docs.lead-knight.com/en/getting-started/create-account/) for account entry and confirmation guidance. Notification, language and appearance preferences are separate: see [Settings](https://docs.lead-knight.com/en/settings/overview/). ## If something goes wrong | Symptom | Next step | |---|---| | Sign-in methods cannot load | Check connectivity and use **Retry**; **Sign out and try again** is also offered for recovery. | | Passwords do not match | Re-enter matching new values. | | Password rejected as weak or previously exposed | Choose a stronger password that meets the displayed requirements. | | Confirmation code expired | Request a new one and respect the retry countdown. | | Signed-in identity changed | Sign in again as the correct person before editing. | | Save failed or confirmation is incomplete | Follow the on-screen error; do not assume the password changed. | ## Related pages - [Account overview](https://docs.lead-knight.com/en/account/overview/) - [Personal profile](https://docs.lead-knight.com/en/account/profile/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) ## Sign-in methods and notifications [Sign-in methods and notifications](https://kwqpaiaguxkmadaipfrf.supabase.co/storage/v1/object/public/guide-videos/guides/videos/P7/nadlanite-en-ed9ca67d4869.mp4) 1. Your sign-in and notification choices are in Settings. 2. Sign-in methods shows the email and accounts you sign in with, like Google. 3. To also sign in with a password, click Set or change password. 4. Notifications decide where alerts reach you, besides the bell. 5. Turn email notifications off if you only want them in the app. 6. WhatsApp alerts need a connected WhatsApp number first. --- # Join the affiliate program and share your code Register business details, accept affiliate terms, create a referral code, and choose how to split the customer discount and your commission. Canonical: https://docs.lead-knight.com/en/account/earn/ ## What this is for The **Earn** page opens **Earn with LeadKnight**. When available, the affiliate program lets you share a code with customers. The code can give a first-payment discount while earning you a commission on qualifying paid charges, subject to your contract. Registration or a trial alone is not a paid commission event. ## Before you start If you don't see **Earn** in the menu, it isn't enabled for your workspace yet. The page can also show **The program isn't open yet**. Prepare your business type and a valid Israeli business number, and read **Affiliate terms** before joining. ## Join and create a code 1. Open **Earn** and review the rules shown. They explain the discount/commission split, payout conditions and number of qualifying customer payments. Your contract can differ from the displayed introductory defaults. 1. Choose **Business type**: **Exempt dealer**, **Licensed dealer** or **Company**. Enter **Business number**. 1. Select **I agree to the affiliate terms** and choose **Join the program**. On success the active-account controls appear. 1. Under **Create your code**, review or enter **Code**. It must contain 4–20 English letters or digits. The suggested code is editable before creation. 1. Move **Customer discount** to choose the first-payment discount. Read the live summary of what the customer gets, your commission on each qualifying payment, and the payment count. 1. Choose **Create code**. Once created, the page displays the code, its expiry and inactivity deadline. 1. Choose **Copy** and share that code with the intended customer. If copying fails, select and copy it manually. The customer must actually apply an eligible code in the billing flow; sharing it is not proof of attribution. ## Change the split and track referrals For an existing code, change **Customer discount**, review the updated summary and choose **Save**. The page explicitly says this applies to customers who use your code from now on. It does not retroactively rewrite existing referrals. **Your contract** shows your maximum discount, commission pool and payments per customer. Use those actual values instead of assuming every affiliate has the same terms. **Customers**, **Earned** and **On hold** summarize activity. The customer list uses anonymous labels such as a customer number and shows payment count and status, not a directory of customer identities. The UI describes code expiry and revocation after 31 days without use. Check the dates on your own code. See [Affiliate payouts](https://docs.lead-knight.com/en/account/affiliate-payouts/) for when recorded commission can actually be paid. ## Business details, leaving and suspension Use **Edit business details** to correct your registered business information and **Save** to submit it. **Leave the program** shows a confirmation that the code stops working while money already earned remains payable subject to requirements. Leaving and rejoining does not restart existing referrals; the page says they stay stopped. A suspended account requires administrator restoration. If the program is closed to changes, recorded earnings remain available for viewing; repeating the join action does not reopen it. ## If something goes wrong | Symptom | What to do | |---|---| | Invalid business number | Check that the Israeli business number is correct; do not enter an invented number. | | Terms not accepted | Read and accept the affiliate terms before joining. | | Code refused | Use the allowed length and characters, and read the specific server refusal before choosing another. | | No customers yet | A shared code alone does not mean a customer used it and paid. | | Commission is on hold | Review the contract and payout requirements, not just the earned total. | | Program closed or account suspended | Follow that status; only the authorized program administrator can restore suspended access. | ## Related pages - [Affiliate payouts and documents](https://docs.lead-knight.com/en/account/affiliate-payouts/) - [Account overview](https://docs.lead-knight.com/en/account/overview/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) --- # Track affiliate payouts and documents Read earned and held commission, check payout requirements, and upload the invoice or withholding certificate requested. Canonical: https://docs.lead-knight.com/en/account/affiliate-payouts/ ## What this page explains Recorded affiliate commission is not the same as a completed payout. The Earn page distinguishes earnings, holds, documents and payout history. Payout controls appear only when the page supplies the relevant payout information; they are not a promise that payouts are enabled for every account. ## Before you start Join the program and review **Your contract** on **Earn**. Have the business documents requested for your account. The program's introductory rules say commission becomes payable after 30 days with monthly payouts on the tenth, subject to requirements; the actual contract and payout status are what matter for your account. ## Review amounts and holds 1. Open **Earn** and compare **Earned** with **On hold**. A hold can prevent payment even though commission is recorded. 1. In **Payout history**, inspect the payout date, amount, withheld tax, sent amount and invoice status where shown. 1. Read any hold message. The interface can require a saved card, a withholding certificate, an accepted invoice, a minimum amount or resolution of an earlier payment. 1. Follow the action for that specific requirement rather than assuming another referral will release it. The UI says commission below ₪100 rolls over to a later payout. A previous unresolved payout holds later payouts until it is resolved. **Processing** or **Awaiting resolution** is not **Paid** or **Confirmed paid**. ## Upload the requested invoice or receipt 1. Find **Invoice required**. Check which document is requested: **Receipt (קבלה)** or **Tax invoice receipt (חשבונית מס קבלה)**. 1. Copy the exact recipient, date requirement and amount shown. For a tax invoice receipt, check **Before VAT**, **VAT** and **Invoice total** separately. 1. Prepare a nonempty PDF, up to 10 MB. Do not upload an unrelated document simply to clear the banner. 1. Choose **Upload invoice** and select the PDF. If the screen offers email delivery, use its displayed destination and send from your LeadKnight account email. 1. Wait for the upload confirmation. It explicitly says document checks and certificate review may take time; upload completion does not instantly accept the invoice or release a hold. 1. If **Last invoice rejection** appears, read the reason and any expected-versus-found amount detail. Correct the document and upload the replacement. ## Upload a withholding certificate 1. Find **Withholding certificate** and review its current status, rate and **Valid until** where present. 1. Choose **Upload certificate** and select the required PDF, up to 10 MB. 1. Check for **Pending review**, **Approved**, **Rejected** or **Superseded**. Only a completed upload is not an approval. Replace an expired certificate when the screen requests it. ## Payment method and program changes If the page asks you to **Add a card in Billing to get paid**, use [Billing](https://docs.lead-knight.com/en/billing/overview/) and return to inspect the payout status. Where supplied, the page identifies the saved payout card by its ending. Never send card details in a document or support message. Leaving the program disables your code but does not erase recorded earned commission. It also does not waive invoice or certificate requirements. See [The affiliate program](https://docs.lead-knight.com/en/account/earn/) for leaving and rejoining rules. ## If something goes wrong - File refused: use a real, nonempty PDF within the displayed size limit. - Invoice hold remains after upload: checks can still be pending; read the status and any rejection. - Amount mismatch: match the precise expected before-VAT, VAT and total fields shown. - Missing or expired certificate: upload the current certificate and wait for review. - Payout unresolved: follow the status and contact support if necessary; do not assume another payout has succeeded. - No payout controls: this part of the program may not be available for your account yet. ## Related pages - [Join and manage the affiliate program](https://docs.lead-knight.com/en/account/earn/) - [Account overview](https://docs.lead-knight.com/en/account/overview/) - [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) --- # Rate your experience and send feedback Answer an available in-app rating request, explain what did not work, or respond to the optional review and video-testimonial offers. Canonical: https://docs.lead-knight.com/en/account/feedback/ ## What this is for The rating page collects a response to an available in-app experience request. Its question names the relevant brand. It is not a general account-settings form and does not always have an open request. ## Before you start Open the rating request while signed in to the intended account and workspace. Think about what worked and what could improve. Do not include passwords, full card numbers or another person's private information in written feedback. ## Submit your rating 1. Open the rating page. If there is no current request, you see **Nothing to rate right now** and **Back to home** instead of stars. 1. When a request is available, read the experience question and choose one to five stars. Choosing a star submits that rating immediately; there is no separate initial Send button. 1. Wait for the page to load the next step. It adapts to the rating recorded. ## If the rating is one, two or three stars 1. The page asks **What wasn't good?**. 1. Enter a useful explanation. The text field is required for this step, ignores blank-only feedback and accepts up to 2,000 characters. 1. Choose **Send**. After saving, one- and two-star responses receive **Thank you, we'll get back to you**; a three-star response receives **Thanks for the feedback!**. A thank-you is confirmation of the saved response, not a guarantee that the reported problem has already been fixed. ## If the rating is four or five stars 1. If a Google review link is available, the page offers **Write a Google review**. Choosing it opens the external review page in another tab; choosing **Skip** moves past that offer. 1. The next offer asks whether you want to record a short video testimonial in exchange for two additional free weeks. 1. Choose **Yes, gladly** or **No thanks**. Accepting records your interest and shows **Great! We'll be in touch soon**. This page does not record/upload a video and does not itself confirm that extra weeks have already been applied. The Google-review button records that you opened the link; it does not prove a review was posted. Both follow-up offers are separate from the star rating already submitted. ## If something goes wrong | Symptom | What to do | |---|---| | No rating request | Use **Back to home**. The form only appears for an available request. | | Rating request cannot load | Check connectivity and choose **Retry**. | | Answer could not be saved | Use **Retry** to refresh the request and follow the current step. Do not assume a failed response was accepted. | | Send is disabled for written feedback | Enter nonblank text and wait for the current request to finish. | | Google review tab did not open | Check browser popup/new-tab restrictions or use **Skip**. | | Expecting a video-upload screen | This step only records whether you are interested; wait for the stated follow-up. | ## Related pages - [Account overview](https://docs.lead-knight.com/en/account/overview/) - [Troubleshooting](https://docs.lead-knight.com/en/troubleshooting/overview/) --- # Developers — API, webhooks and AI connector Choose a server-side API integration, signed event notifications, or the future Claude and ChatGPT connector, and understand their separate credentials and permissions. Canonical: https://docs.lead-knight.com/en/developers/overview/ ## Choose your integration LeadKnight offers personal server-side Developer API keys and signed webhook notifications. The separate AI connector for Claude and ChatGPT is **not available yet**. The connector instructions describe what to do once it is turned on; an API key does not enable that connector. | Your goal | Start here | Credential or setup | | --- | --- | --- | | Connect your own backend, CRM sync or reporting service | [Developer API](https://docs.lead-knight.com/en/developers/developer-api/) | Create a personal key in **Settings → Developer API**; send it from your server only. | | Receive contact changes and campaign status changes without repeatedly polling | [Webhooks](https://docs.lead-knight.com/en/developers/webhooks/) | Add a public HTTPS receiver in Settings and save its one-time signing secret. | | Work in a workspace from Claude or ChatGPT after the connector becomes available | [AI connector](https://docs.lead-knight.com/en/developers/ai-connector/) | Copy the address from Settings, connect using OAuth and choose one workspace on the consent page. | | Give the future connector photos or videos from your device | [Connector uploads](https://docs.lead-knight.com/en/developers/connector-upload/) | Open the upload link supplied in the conversation, upload in the correct workspace and return to the conversation. | | Look up exact operations, request fields, response shapes and webhook bodies | [API reference](https://docs.lead-knight.com/en/developers/api-reference/) | Read the reference; use the [live OpenAPI document](https://api.lead-knight.com/developer-api/openapi.json) for machine-readable contracts. | ## Before connecting anything 1. Sign in with the person whose access the integration should use. Select the intended workspace before creating a key or webhook. 2. Confirm that this person has the current role, seat and access needed for the operation. A key or connection acts as that person; it cannot preserve access after membership or permissions change. 3. Decide whether the integration only reads, edits drafts and CRM records, or also publishes and controls work. Choose the least powerful API key that meets the need. 4. Prepare private server-side secret storage for API keys and webhook signing secrets. Do not put them in browser code, mobile apps, URLs, shared screenshots, source control or logs. 5. Read the relevant how-to before enabling a write or send. A successful API response, campaign status or webhook is not proof that content was delivered to a social network or recipient. ## Three mechanisms, not interchangeable credentials ### Personal Developer API keys An API key belongs to one person and one workspace. The HTTPS resource base URL is `https://api.lead-knight.com/v1`; resource calls use `Authorization: Bearer <key>`. Its `read`, `write` or `publish` ceiling is combined with the person's current role and seat. The key does not sign in to the app, manage other keys or authorize a Claude/ChatGPT connection. Start with a read-only request. For mutations, retain the reviewed request and any required operation key before sending. Follow the [Developer API recovery rules](https://docs.lead-knight.com/en/developers/developer-api/) rather than automatically repeating a request with an uncertain result. ### Signed outbound webhooks Webhooks send HTTPS POST requests from LeadKnight to your receiver. They have a separate `whsec_` signing secret, not an API bearer key. Verify signatures over the original raw body, check the attempt timestamp and deduplicate delivery IDs before applying changes. Deliveries can repeat and do not provide a complete change-history or social-delivery feed. Use the [webhook guide](https://docs.lead-knight.com/en/developers/webhooks/) for endpoint requirements, event selection, signature verification, retries and disabled endpoints. ### Future AI connector The connector uses OAuth consent, not a personal API key. Each connected app is bound to one person and one chosen workspace. Its actions do not show LeadKnight approval cards: once available, review and explicitly confirm risky instructions in the host conversation before asking it to act. Paid-ad launch and billing changes remain inside LeadKnight. The connector is not a replacement for the in-app assistant's approval flow. See [AI connector availability and setup](https://docs.lead-knight.com/en/developers/ai-connector/) and the separate [upload workflow](https://docs.lead-knight.com/en/developers/connector-upload/). ## If something goes wrong | Symptom | What to check | Next step | | --- | --- | --- | | You cannot see **Developer API** or **Webhooks** | Availability and your current workspace access; disabled features with no existing items can be hidden. | Check the intended workspace and current permissions. Existing keys or endpoints may still be visible for revocation or deletion. | | The Claude/ChatGPT connector card or address is missing | The connector is not available yet; setup details are hidden while disabled. | Do not substitute an API key or invent a connector URL. Use the Developer API for supported server-side work. | | A request works for one person but not another | Keys and webhook visibility use each person's own current access. | Check membership, role, seat and ownership/sharing, not only the key's selected ceiling. | | A write times out | The server may already have completed it. | Inspect the current state and follow the applicable API or connector recovery instructions before sending anything again. | | The webhook is accepted but your receiver applies a change twice | Delivery is at least once. | Store and deduplicate `webhook-id`, and acknowledge verified duplicates without repeating side effects. | ## Related pages - [Create and use Developer API keys](https://docs.lead-knight.com/en/developers/developer-api/) - [Receive and verify webhooks](https://docs.lead-knight.com/en/developers/webhooks/) - [Connect Claude or ChatGPT when available](https://docs.lead-knight.com/en/developers/ai-connector/) - [Upload photos and videos for the connector](https://docs.lead-knight.com/en/developers/connector-upload/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) - [API reference](https://docs.lead-knight.com/en/developers/api-reference/) - [Live OpenAPI document](https://api.lead-knight.com/developer-api/openapi.json) --- # Create and use a Developer API key Create a personal server-side key, choose read/write/publish access, call the API safely, paginate results, respect quotas and recover from uncertain writes. Canonical: https://docs.lead-knight.com/en/developers/developer-api/ ## What this is for Use the Developer API to connect your own backend to LeadKnight: read campaigns, posts, accounts, destinations, media, analytics and posting activity; maintain CRM contacts; upload media; and create, publish or control reviewed campaign work when authorized. It is a server-to-server API, separate from the future Claude/ChatGPT connector. The production resource base URL is `https://api.lead-knight.com/v1`. Keep the `/v1` prefix on resource requests. The [API reference](https://docs.lead-knight.com/en/developers/api-reference/) describes exact operations and fields. The public [OpenAPI document](https://api.lead-knight.com/developer-api/openapi.json) is outside `/v1`, requires no key and contains no account data; it is unavailable when the Developer API is disabled. ## Before you start - Sign in as the person the integration should act as, select the correct workspace and confirm the current role and seat allow the intended operations. - Prepare a backend and private secret manager or server environment. Do not put the key in browser JavaScript, a mobile app, a URL, source control, analytics or logs. - Choose the minimum key permissions. A key belongs to one person and one workspace; it is not a workspace-wide administrator credential. - For publication, first connect and authorize the actual accounts, destinations and recipients. API access does not grant missing account access, recipient consent, sender permissions or platform eligibility. If you do not see **Developer API** in Settings, it may not be enabled for your workspace yet. When globally disabled, a card with no existing keys is hidden; existing personal keys remain listed and revocable, but creation and API use are disabled. ## Create the key in Settings 1. Open **Settings → Developer API**. Check **API base URL** and open **API documentation (OpenAPI)** if you need the machine-readable contract. 2. Select **Create API key**. The dialog shows **Workspace**. Verify it before continuing; changing a request header later cannot move this key to another workspace. 3. Enter **Key name**, identifying the backend or app. Use 1–100 characters without control characters or invalid Unicode. Invalid names show a message you can correct before creation. 4. Under **Permissions**, choose one of the levels below. The default is **Read only**. 5. Under **Key lifetime**, choose **30 days**, **90 days**, **180 days**, **1 year** or **No expiry**. The default is **90 days**. No expiry does not survive revocation, lost membership or loss of current permissions. 6. Select **Create API key**. On success, **Save your API key now** replaces the form and identifies the workspace. The **One-time API key** is the only chance to see the secret. 7. Select **Copy key** and save it privately on your server. If copying fails, the selected field can be copied manually; you can also select **Copy key** again. Do not close the dialog before saving. 8. Select **I've saved the key**. Under **Your API keys**, confirm the name, workspace, permission level, masked prefix/last four characters, expiry and last-use information. **Load more** loads further keys. Closing the secret dialog, leaving the screen, or changing identity/workspace discards the displayed secret. It cannot be recovered. If creation reports an uncertain result or the secret was lost, use **Refresh list**, revoke any new key you did not save, and create a replacement. Do not repeatedly submit key creation to find out whether the first request worked. ### Choose the correct permission ceiling | Settings option | API value | What it permits, subject to current access | | --- | --- | --- | | **Read only** | `read` | Supported resource reads. No uploads, CRM changes or publishing. | | **Read and write** | `write` | Includes read, CRM creation/updates/notes, uploads, standalone draft campaigns and unarmed post drafts. | | **Read, write and publish** | `publish` | Includes read and write, plus explicit publication, pause/resume/archive and edits to already-granted or started work. | Editing a previously granted or started post requires publish authority even if the new request says `intent: "draft"`: withdrawing a grant can cancel work. The same principle applies to campaign edits after approval or execution history exists. A key's ceiling never bypasses the person's current role, seat, visibility or channel rules. Limited preparation-state allowances do not grant publishing rights. ## Make a first server-side read 1. Load the stored key privately into your backend. The token starts with `lk_api_`; do not replace it with a first-party session token or an MCP token. 2. Make an HTTPS `GET` to `https://api.lead-knight.com/v1/campaigns` with `Authorization: Bearer <key>`. Replace the placeholder privately; never put the key in the URL. 3. Inspect the HTTP status, JSON response and rate-limit headers. A successful collection response includes `items` and `nextCursor`. 4. Keep the key's workspace binding. Prefer omitting `X-Workspace-Id`. A conflicting value returns 400 `workspace_mismatch`; that header cannot select a different workspace. 5. Continue with another read operation from the reference before implementing changes or publishing. Requests carrying `Origin`, `Sec-Fetch-Site`, `Sec-Fetch-Dest` or `Sec-Fetch-User` are refused with 401 `browser_request_not_allowed`. This protects against accidental browser use; do not solve it by embedding a key in a different browser transport. Move the integration to your server. A lone `Sec-Fetch-Mode` header from server-side fetch is not refused for that reason. Keys do not authenticate ordinary app APIs or the signed-in key-management endpoints. Use Settings to create and revoke your own keys; being a workspace administrator does not expose another person's keys. ## Supported work and important boundaries | Area | Supported operations and requirements | | --- | --- | | Campaigns and posts | List/read; create a standalone draft campaign; create or fully update a reviewed post; limited campaign edits; pause/resume selected or all cards; archive. Use the exact request shapes in the reference. | | Accounts and destinations | Discover permitted Facebook identities, official connected accounts and destinations. A Facebook identity ID is not an official connected-account ID. Group destinations include the identities that can reach them. | | Media | List visible, attachable media and upload exactly one multipart `file`, with no additional fields. JPEG, PNG, WebP and GIF: up to 10 MiB; MP4: up to 256 MiB. Actual content and type are validated. | | Analytics and activity | Analytics requires ISO datetime `from` and `to`, with `to` later than `from`. Posting activity supports its own date/period/network filters and continuation fields. | | CRM | List/read/create/update visible contacts, change/request ownership, create/delete notes, and read stages and members. At least a phone or email is needed on creation. Visibility and private-field rules remain in force. | | Outbound events | New contact, contact updated and campaign status changed notifications through [Webhooks](https://docs.lead-knight.com/en/developers/webhooks/), configured in Settings. | There are no Developer API operations here for direct paid-AI generation/editing, billing, paid-ad spending, calendar or real-estate-specific CRM fields. Five campaign channels are supported: social feeds, Facebook groups, WhatsApp, email and Marketplace, each with its existing approvals, accounts, sender, media, consent and eligibility rules. Discovery does not include Gmail senders or WhatsApp accounts; do not invent account or recipient IDs. ## Paginate without losing your place 1. Begin a list without a cursor. `limit` defaults to 20, normally accepts 1–50, and allows up to 500 for destinations. 2. Read `items` and retain `nextCursor`. A null cursor means there is no further page in this continuation. 3. Pass a non-null returned cursor unchanged to the same collection with the same relevant filters and identity/workspace. Do not decode, construct or round its timestamps. Cursor length is limited to 2,048 characters. 4. For campaign-post lists, retain the same parent campaign. For destinations, retain the bound destination filters. If the server returns 400 `invalid_cursor`, restart the correct list instead of repairing the cursor. 5. Treat pagination as a changing live collection, not a snapshot. Records can change between requests. Posting activity has a different envelope: `activity`, `nextCursor` and `bulkSendsNextCursor`. Retain its filters and `limit` with the cursor; the separate bulk-send continuation uses `network=whatsapp`. CRM stage/member directory responses have `items` but are not ordinary cursor-paged collections. Consult the reference for each response rather than assuming every endpoint shares one shape. ## Respect rate limits Default budgets are **60 requests per minute per key** and **1,000 requests per UTC day per workspace and issuing person**, shared across that person's keys. Operators can configure different limits, so use response headers as the authority. The minute window lasts 60 seconds from its first admitted request; the daily window resets at 00:00 UTC. | Header | Meaning | | --- | --- | | `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset` | Per-key minute limit, remaining requests and reset time. | | `X-RateLimit-Day-Limit`, `X-RateLimit-Day-Remaining`, `X-RateLimit-Day-Reset` | Shared daily limit, remaining requests and reset time. | | `Retry-After` | On quota exhaustion, how many seconds to wait. | Reset times are Unix epoch seconds. Authenticated reads, retries, permission/seat refusals and conflicting workspace headers consume budget. Rotation does not reset the shared day budget. Earlier transport/IP refusals may not include developer-quota headers. A 429 means wait for the indicated interval; unavailable quota infrastructure returns 503 rather than allowing unrestricted traffic. ## Make changes without accidental duplicates ### Durable request identity Before sending campaign creation, campaign edits, post writes, pause/resume/archive or note creation, store the method, target, exact reviewed request body and a stable `Idempotency-Key`. Operation keys are 1–255 visible ASCII characters with no spaces. Reuse the same key only for the same logical operation and unchanged body. Receipts survive API key rotation for the same person/workspace; new credentials do not make an old operation new. Contact creation uses required `externalId` instead, 1–200 visible ASCII characters without spaces. It is workspace-wide find-or-create, not an upsert: 201 creates and 200 returns the current readable existing contact without overwriting it. `external_id_in_use` does not disclose an unreadable contact. `duplicate_contact` is a separate existing phone/email match and can include the existing `contactId`. Uploads do not have an idempotency guarantee. Repeating an upload can create another asset. Unused staged assets become cleanup-eligible after 24 hours; do not treat an upload link or temporary URL as permanent storage. ### Reviewed content and publication 1. Create the draft campaign and retain its returned ID. 2. Upload needed media and retain real asset IDs. Select currently authorized accounts, destinations and consenting recipients. 3. Assemble and review the full post, complete desired channel-card set, schedules and channel-specific consent/caps. Use `intent: "draft"` to save without granting sends or `intent: "publish"` to explicitly approve that exact content and configuration. A schedule of now may stage work immediately. 4. For updates, retain the reviewed `expectedRevision`. A `PUT /v1/posts/{id}` replaces desired post/card state; it is not a partial patch. Include stored card IDs to retain them and omit an old card only when intentionally removing it. 5. Retain your original reviewed configuration. Public GET omits private card configuration, recipient and sender selections; it is not an editable template. Never copy GET straight into PUT or silently combine a new revision with old content. 6. Inspect returned per-card outcomes and later activity. Accepted work can set an unavailable channel aside; a current grant or active/finished card is not proof of external delivery. An uncertain response is not proof of failure. Inspect current state first. Deliberate replay of a keyed operation keeps the original method, target, body, operation key and reviewed revision. Do not add automatic write/upload retries. A new edit needs a new review and operation key, not a modified consumed request. Pause and archive stop eligible future/stoppable work; they cannot recall provider requests already in flight, delete already-published content or stop independent paid-ad budgets. ## Read errors and recover Errors are flat JSON with `error` and `message`, not a nested provider error. Validation may include `details.issues` with up to eight safe path/message entries; `requestId` is optional. Keep the HTTP status along with the error token. | Status or symptom | Meaning and next step | | --- | --- | | 400 | Invalid input, header or cursor. Remove unknown fields and correct the documented shape; restart a mismatched list. | | 401 | Invalid/expired/revoked key, lost membership or forbidden browser transport. Check the server-side credential and current membership; do not expose the key while debugging. | | 403 | Current key ceiling, role, visibility or seat does not permit the operation. Fix actual access rather than repeatedly retrying. | | 404 | Resource absent/inaccessible or API disabled. Confirm the base path, real IDs and availability. | | 409 `operation_key_conflict` | A consumed key is being used with changed content/action. Recover the original request; use a new key only for a genuinely new operation. | | 409 `post_changed` | Reviewed revision is stale. Inspect current status, reconcile retained configuration, review again and submit a new operation. Do not blindly increment the revision. | | 409 `posting_busy` with `retryable: true` | The edit rolled back because cancellation was contended. After contention clears, deliberately retry the same full request/key. | | 409 `archive_cleanup_incomplete` with `retryable: true` | The campaign is archived but cancellation is incomplete. Repeat the same archive request/key to finish cleanup; do not reactivate it. | | 410 | A consumed resource was deleted. Replaying its key cannot create a replacement. | | 413 / 415 | Upload too large / unsupported type. Prepare a supported real file within its bound. | | 422 | Domain refusal, such as a send exceeding its approved cap. Review and correct the business request. | | 429 | Wait according to `Retry-After` and quota reset headers. | | 500 / uncertain write | Outcome may be unknown. Inspect state before any deliberate same-key replay. Never assume the write failed. | | 503 | A required dependency is unavailable. Preserve your operation journal and avoid an uncontrolled retry loop. | The `retryable` flag is not present on every error; absence is not permission to repeat a mutation unchanged. ## Rotate or revoke a key 1. Create a replacement with the minimum permissions and suitable expiry. 2. Store it privately, update the backend and confirm the replacement can make the intended read. 3. Under **Your API keys**, select the old key's **Revoke**. Review **Revoke {name}?** and the warning that apps lose access immediately. 4. Confirm **Revoke**. The key becomes **Revoked** and cannot be restored. **Expired** keys also cannot authenticate. 5. If revocation's outcome is uncertain, use **Refresh list** to check the state before repeating it. If a key leaked, revoke it rather than relying on expiry. ## Webhook signatures and related pages For signed event delivery, add a webhook in Settings rather than sending a bearer key to the receiver. Verify `webhook-id`, `webhook-timestamp` and `webhook-signature` over the raw body using the separate `whsec_` secret. Check a five-minute timestamp tolerance, compare HMAC signatures in constant time and deduplicate IDs durably for 30 days. The [webhook guide](https://docs.lead-knight.com/en/developers/webhooks/) gives the exact signing construction and delivery behavior. - [Developers overview](https://docs.lead-knight.com/en/developers/overview/) - [Webhooks setup and verification](https://docs.lead-knight.com/en/developers/webhooks/) - [AI connector — not available yet](https://docs.lead-knight.com/en/developers/ai-connector/) - [Connector uploads](https://docs.lead-knight.com/en/developers/connector-upload/) - [API reference](https://docs.lead-knight.com/en/developers/api-reference/) - [Live OpenAPI document](https://api.lead-knight.com/developer-api/openapi.json) --- # Receive and verify signed webhooks Add an HTTPS endpoint, select contact or campaign events, save the one-time signing secret, verify raw-body signatures and handle retries or disabled delivery. Canonical: https://docs.lead-knight.com/en/developers/webhooks/ ## What webhooks do A webhook sends a signed HTTPS POST from LeadKnight to your server when a selected CRM contact or campaign status changes. Use it to update another system without repeatedly polling the Developer API. It is an outbound notification, not an incoming command, and it does not need a personal API key in its receiver URL. Webhooks are available wherever the Developer API is enabled. They are managed in Settings using your signed-in account, not through an API key. Each endpoint belongs to the person who created it in one workspace and carries only data that person is currently allowed to see. ## Before you start - Prepare a public HTTPS receiver on port 443 or 8443 with a valid TLS certificate. The URL may contain no credentials or fragment and may be at most 2,048 characters long. - Ensure every IP address the hostname resolves to is public. A public hostname with even one private/internal result is not accepted; public-address validation also happens before delivery. - Configure the receiver to retain the exact raw request body before JSON parsing and to accept POST requests without redirecting. - Prepare private server-side secret storage, a synchronized clock, durable delivery-ID deduplication and a queue for slower processing. - Sign in as the intended endpoint owner and select the correct workspace. Current role, seat and contact visibility still apply. You can have at most five live webhooks per person per workspace. If **Webhooks** is missing, it may not be enabled for your workspace yet. While the Developer API is disabled, existing endpoints stay visible for deletion; a card with no endpoints is hidden. Do not publish a receiver secret in source control, request URLs, logs or screenshots. ## Add the endpoint 1. Open **Settings** and find **Webhooks** alongside **Developer API**. **Your webhooks** shows the endpoints belonging to your account. 2. Select **Add webhook** and verify the displayed **Workspace**. 3. Enter the final receiver address in **Webhook URL**. Use the actual HTTPS POST URL, not a login page or an address that redirects to another path. 4. Under **Events**, select at least one of **New contact**, **Contact updated** and **Campaign status changed**. You can select more than one for the same endpoint. 5. Select **Save**. On success, the **Signing secret** dialog appears. Use **Copy** and save the `whsec_` secret in your server's secret manager. It is shown only once. 6. If copying fails, copy the selected field manually or select **Copy** again. Select **I've saved the secret** only after it is stored. Closing or leaving the page loses access to the displayed secret. 7. Find the new URL under **Your webhooks**. Check its workspace, event badges, state and **Last delivery**. 8. Configure the receiver's verifier using that endpoint's secret, then select **Send test event**. A successful receiver returns a display such as **Delivered (200)**; other successful 2xx statuses are also accepted. The test body is `webhook.test`, not a new contact or actual campaign change. If creation is uncertain or you lose the secret, use **Refresh list**, delete any newly created endpoint whose secret you did not save, and add it again. Do not automatically repeat creation: the first request might already have succeeded. Secrets cannot be displayed again; replacing a secret requires deleting and recreating the endpoint. ## Choose events and understand the payload Every body contains `type`, ISO datetime `timestamp` and `data`. The attempt header `webhook-timestamp` is a separate Unix-seconds value used for signature verification. Use the [API reference](https://docs.lead-knight.com/en/developers/api-reference/) or the top-level `webhooks` section of the [OpenAPI document](https://api.lead-knight.com/developer-api/openapi.json) for full field definitions. | Settings event | Body `type` | When and what is sent | | --- | --- | --- | | **New contact** | `contact.created` | A CRM contact is created, including an audience member promoted to a contact. `data.contact` uses the safe Developer API contact projection. | | **Contact updated** | `contact.updated` | Changes to name, email, phone, owner, stage, loss reason, deal value/currency, tags or custom values. `data.contact` is current state when the delivery is prepared. | | **Campaign status changed** | `campaign.status_changed` | A derived campaign status change; `data.campaign` is the API campaign summary and `data.previousStatus` is the previous status. Checks run about once a minute, so a shorter-lived state can be missed. | | **Send test event** | `webhook.test` | A manual receiver check with `data.test` set to true. It does not prove that a real contact is visible to this endpoint's owner. | Closely spaced contact changes can produce a single notification. This is not an immutable log of every edit. Contact data is limited by the endpoint owner's current visibility; private categories that are no longer accessible are not sent. Deleted and merged-away contacts produce no contact payload. Membership, role/seat and category access are rechecked before delivery, including retries. Campaign status is not a delivery receipt from a social network. Do not mark a recipient contacted or a post delivered solely because a status-change event arrived. ## Verify every request before using its data Deliveries follow [Standard Webhooks](https://www.standardwebhooks.com/). Use the endpoint's signing secret, not a Developer API key. | Header | Meaning | | --- | --- | | `webhook-id` | Unique delivery ID. Retries retain the same ID and body. | | `webhook-timestamp` | Unix seconds for this particular attempt. | | `webhook-signature` | Versioned signature, `v1,` followed by a base64 HMAC-SHA256 value. | 1. Read the raw request body exactly as received. Do not parse and reserialize JSON before verifying: whitespace, escaping or character changes alter the signature. 2. Require a delivery ID, a valid numeric attempt timestamp and a versioned signature. Reject a timestamp more than five minutes away from your server's clock; do not confuse Unix seconds with milliseconds. 3. Remove the `whsec_` prefix from the stored secret and base64-decode the remaining text to obtain the HMAC key. Do not use the prefixed secret text directly as the key. 4. Construct the signed input as `<webhook-id>.<webhook-timestamp>.<raw body>`, with periods between the three parts, using the exact header values and original body. 5. Calculate HMAC-SHA256 with the decoded key and base64-encode the result. Match the `v1,` signature value using a constant-time comparison. If the signature header contains space-separated candidates, accept only a valid matching supported candidate. 6. Reject unverifiable or stale requests before applying business changes. Never bypass verification just to make a test display as delivered. 7. After verification, deduplicate `webhook-id` durably for 30 days. An already-accepted delivery should receive a successful acknowledgement without repeating side effects. 8. Parse and validate the event, safely persist or queue it, and return any 2xx within ten seconds. Perform longer processing after acknowledgement, with your own durable recovery so acknowledged work is not lost. Each retry has a fresh attempt timestamp/signature but the same delivery ID and body. A body timestamp can therefore be older than its request timestamp; verify the attempt header, not the event's age, for the five-minute check. ## Delivery rules and recovery - Delivery is at least once. A response can be lost after your receiver processed a request, so duplicate handling is required even when your receiver normally succeeds. - There is no ordering guarantee across contacts. Use payload state rather than assuming global arrival order is the edit order. - Return 2xx within ten seconds. Redirects are not followed; 3xx, other unsuccessful statuses, connection/TLS failures and timeouts count as failures. - Failed delivery retries wait 1 minute, 5 minutes, 15 minutes, 1 hour, 3 hours, 6 hours and 12 hours after the successive failures. That is eight attempts including the original, spanning about 22.5 hours plus request processing. - While enabled with a failed latest attempt, the endpoint shows **Failing**. After the last failed attempt, it becomes **Disabled** and its owner is emailed. - Fix the receiver before selecting **Enable**. This resets failure state but does not replay abandoned deliveries or changes missed while off. Reconcile current records through the [Developer API](https://docs.lead-knight.com/en/developers/developer-api/) when needed. - Erasing a contact removes pending deliveries. A request already sent to a receiver cannot be recalled. ## Disable, delete or replace an endpoint 1. Find the URL under **Your webhooks**. Use **Disable** to stop delivery without deleting the configuration; its state changes to **Disabled**. 2. Use **Enable** only after the receiver and permissions are ready. Disabling and enabling do not create a history-replay service. 3. To remove the URL permanently, select **Delete**. Read **Delete webhook?** and confirm **Delete**; **Cancel** leaves the endpoint in place. Deletion cannot be undone. 4. To change the receiver URL, event selection through the available creation flow, or replace a lost signing secret, add a correctly configured replacement and remove the old endpoint. The current Settings card has no edit form for an existing URL or event set. Observe the five-endpoint limit and handle potential overlap without applying changes twice. 5. If any management result is uncertain, use **Refresh list** to inspect current state before repeating the action. ## If something goes wrong | Symptom | Likely cause | What to do | | --- | --- | --- | | Invalid URL message | HTTP, disallowed port, credentials, fragment or excessive length. | Use a final public HTTPS URL on 443 or 8443, no credentials/fragment, at most 2,048 characters. | | Public-address refusal | DNS returns a private, reserved or otherwise non-public address. | Correct every DNS result; a localhost or internal receiver cannot be used. | | No event selected | The form requires at least one event. | Select the appropriate **Events** before **Save**. | | Five-endpoint limit | This person's live endpoints in the workspace reached the cap. | Delete an obsolete endpoint before adding another. | | **Delivered (200)** but no real updates | A test verifies transport, not the selected events or visibility of a record. | Check event badges, actual changes, workspace and owner access. | | Signature mismatch | Wrong endpoint secret or body changed by middleware. | Keep the original bytes, decode the secret after `whsec_` and use the exact three signed parts. | | Timestamp rejected | Clock drift or seconds interpreted as milliseconds. | Synchronize the receiver clock and check `webhook-timestamp` in seconds. | | Timeout | The receiver did not complete within ten seconds. | Verify, durably queue and acknowledge promptly; move long work out of the request. | | TLS, connection or redirect error | Unreachable server, invalid certificate or forwarding URL. | Fix connectivity/TLS and use the final non-redirecting endpoint, then send a test. | | **Disabled** after repeated failures | All delivery attempts failed. | Repair the receiver, test it and select **Enable**; reconcile missed state separately. | | Secret lost or creation uncertain | The one-time secret is no longer available. | Refresh, delete that endpoint and add it again; do not guess or recover a secret from logs. | ## Related pages - [Developers overview](https://docs.lead-knight.com/en/developers/overview/) - [Developer API keys and recovery](https://docs.lead-knight.com/en/developers/developer-api/) - [Contacts and CRM](https://docs.lead-knight.com/en/contacts/overview/) - [Campaigns](https://docs.lead-knight.com/en/campaigns/overview/) - [API reference](https://docs.lead-knight.com/en/developers/api-reference/) - [Live OpenAPI document](https://api.lead-knight.com/developer-api/openapi.json) --- # AI connector for Claude and ChatGPT — not available yet The AI connector is not available yet. Learn the future setup, OAuth consent and workspace choice, action limits, file uploads and how to disconnect a connected app. Canonical: https://docs.lead-knight.com/en/developers/ai-connector/ ## Availability — read this first > **Important:** The Claude/ChatGPT AI connector is **NOT AVAILABLE YET**. All setup steps below apply only once the connector is deliberately turned on. A Beta label or an existing help page does not mean that it is ready to connect today. The connector is separate from the available [Developer API](https://docs.lead-knight.com/en/developers/developer-api/). Do not create a personal API key to connect Claude or ChatGPT. Do not change advanced settings or use an invented endpoint to bypass unavailable consent. When disabled, Settings hides the connector address and setup instructions. If you have no existing connected apps, the entire card is hidden. Existing connections can still be listed and disconnected. If you do not see the connector in Settings, it is not enabled for your workspace yet. ## What the connector will let you do The connector uses MCP and OAuth to let a supported Claude or ChatGPT installation act as you in one selected LeadKnight workspace. Available tools can read campaigns, contacts, calendar and results and create, publish or change supported content, subject to your current membership, role, seat and feature availability. | Boundary | What it means | | --- | --- | | One person and one workspace per connected app binding | The workspace is chosen during consent, not by putting another workspace in a chat instruction or tool argument. | | Current access, not permanent delegated privileges | Removed membership or revoked permissions stop the corresponding access. A connection does not grant access to another person's private records or unshared accounts. | | No LeadKnight approval cards for connector actions | Calls can execute immediately. The host app is instructed to ask you before publishing, sending, deleting or archiving, but LeadKnight does not enforce the host's conversational confirmation. Review consequential instructions before giving them. | | App-only operations | Paid-ad launch/discard and billing changes remain inside LeadKnight. Direct LeadKnight-paid generation, research/vision and internal assistant tools are not exposed through the connector. | | Existing product rules still apply | Accounts, recipient consent, sender permissions, media access, scheduling, quotas and supported workspace features remain authoritative. Ordinary content changes may still trigger the product's existing background maintenance; the connector is not a guarantee of zero incidental processing. | The in-app assistant keeps its existing approval flow. Connecting an external AI app does not change those in-app rules or grant the host unrestricted access to every API route. ## Before setup becomes available - Have your LeadKnight sign-in and at least one set-up workspace ready. The consent screen can direct you to finish workspace setup if none exists. - Check your current role, seat and relevant connected accounts in that workspace. - Use a supported Claude account or ChatGPT workspace with custom MCP connection access. The current setup copy lists ChatGPT Business, Enterprise and Edu for the connector; Pro is read-only. Host workspace permissions can also affect whether creation is offered. - Decide exactly which workspace the host should use. Check the name during consent even if you normally work in a different workspace in the app. - Understand that external AI software receives data through the tools you authorize and can change supported content as you. Disconnect an app you no longer trust. ## Copy the connector address once enabled 1. Open **Settings** and find **Use LeadKnight in Claude & ChatGPT**, marked **Beta**. The product name in this heading follows your workspace branding. 2. Locate **Connector address** and select **Copy**. **Copied** confirms clipboard success. If copying fails, select the address and copy it manually. 3. Paste that exact address into the host's MCP connector configuration. It is the configured HTTPS MCP server address, serving `/mcp`, not the web-app homepage, `/oauth/consent`, the Developer API `/v1` address or an OpenAPI URL. 4. If the address is missing, stop setup: the connector is not enabled. This guide does not provide a hardcoded production connector URL because the address must come from the enabled Settings card. ### Claude setup once enabled 1. In Claude, open **Settings → Connectors**. 2. Select **Add custom connector** and paste the copied **Connector address**. 3. Choose **Add → Connect**. Claude starts the authorization journey and opens the LeadKnight sign-in/consent page. 4. Complete the workspace and permission review below. Successful consent returns you to the host; an existing valid authorization can return you without showing a fresh decision form. ### ChatGPT setup once enabled 1. In ChatGPT, open **Plugins → + → Add custom MCP server**. 2. Enter a name, paste the copied address under **Connection** and select **OAuth**. 3. Review the host's risk warning and, if you agree, select **Create as a plugin**, then connect. 4. Complete LeadKnight consent. If your host plan or workspace does not offer this setup, check that host's eligibility rather than trying an API key or a different authentication mode. These host-menu names are the instructions currently shown in LeadKnight; third-party menus and eligibility can change. Do not treat unavailable host options as evidence that LeadKnight consent has succeeded. ## Review consent at /oauth/consent The consent route is `/oauth/consent`. Open it from the connection you just started in Claude or ChatGPT. It requires the host-generated `authorization_id`; opening the bare route is not a way to create authorization. 1. If signed out, sign in on the LeadKnight page. You return to the pending authorization after signing in. 2. If there are no workspaces, follow **Set up your workspace**, finish onboarding and restart the connection from the host. 3. On **Allow {clientName} to use {brand}?**, inspect the app name and **Returns to {host}**. Read the warning: **Only continue if you started connecting from Claude or ChatGPT yourself just now.** Names and a return host are information to review, not proof that an unsolicited link is safe. 4. Under **Workspace**, choose the one workspace this app may act in. Review the description: the connection includes reading and supported creation/publication/changes, not a read-only checkbox selection on this screen. 5. Select **Allow** only if the app, return host and workspace are the ones you intended. The screen shows **Returning you…** and navigates back to the host when authorization completes. 6. Select **Deny** if you did not initiate the connection or do not agree. It returns to the host when a return URL is provided, or shows **Cancelled. You can close this tab.** No new permission should be assumed from a cancelled journey. 7. After success, return to Settings and inspect the connected-app row: app name, workspace, **Connected {date}** and **Last used {when}**. Start with a read request in the host and check that the results are for the intended workspace. Re-consenting the same OAuth client replaces its local binding with the newly selected workspace. Switching workspaces in the web app later does not redirect an already-bound host connection. To change its target, deliberately reconnect and select the new workspace during consent; do not rely on a chat instruction saying to use another workspace. ## Photos, videos and usage limits Ask the connected app for an upload link when it needs media from your device. Use the link to open `/connector-upload`, complete the upload in the intended workspace, then return and say that you are done. Attaching a file only to the host conversation does not establish that LeadKnight received it. See [Connector uploads](https://docs.lead-knight.com/en/developers/connector-upload/) for statuses, formats, compression and temporary storage. The current connector defaults are 60 bearer requests per minute, with authenticated traffic also limited per live connection, and 1,000 eligible action-tool calls per workspace/person/UTC day. Reconnecting does not reset the shared daily allowance. Email has additional defaults of one validated send call per minute and 20 per UTC day per workspace/person, shared across connections, on top of normal mailbox and recipient rules. These are configurable limits, not entitlements to send without consent. Protocol throttling can return HTTP 429 with `Retry-After`; tool refusals can appear in the host as an error result. Wait for the indicated interval. If an action's outcome is unknown, inspect the current campaign, contact, calendar or sending state before asking again. A new connector invocation is not a replay guarantee of an earlier mutation; do not repeatedly ask the host to resend an uncertain operation. ## Disconnect a connected app 1. Open **Settings** and find the connected-app card. Existing connections remain manageable even when new connector setup is disabled. 2. Check the app and workspace in its row, then select **Disconnect**. 3. Read **Disconnect {clientName}?** and the immediate-access-loss warning. Select **Cancel** to keep it connected or **Disconnect** to revoke it. 4. Local connector access is revoked first. Removal of the upstream OAuth grant is also attempted. If the app still shows LeadKnight as connected, remove it in Claude or ChatGPT too; the Settings note can remain visible after a partial upstream cleanup. 5. If disconnect reports failure, select **Try again** or reload the list and inspect it before assuming the app is disconnected. Disconnecting removes the app's ability to make further connector calls. It is not a request to delete data the host already received or to undo posts/messages/actions already executed. ## If something goes wrong | Symptom | Cause or boundary | Next step | | --- | --- | --- | | No connector card or address | The connector is not available yet or is disabled. | Do not attempt setup until the address is offered in Settings. | | Invalid sign-in link | Missing/invalid `authorization_id` or a hand-built consent URL. | Start a fresh connection in Claude or ChatGPT; do not edit the authorization ID. | | Expired sign-in link | The authorization request is no longer usable. | Restart from the host rather than reusing the old tab. | | Unsupported app message | The requesting client is not supported. | Return to LeadKnight; use only supported host setup once enabled. | | Not a workspace member | Selected/requested workspace is not available to your identity. | Choose a workspace you belong to and check current membership. | | Already connecting | A consent decision is already in progress. | Refresh the page as instructed; inspect the host and Settings before starting duplicates. | | Sign-in service unavailable | The authorization service could not be reached. | Select **Try again**; do not approve a different unsolicited link. | | Wrong workspace in results | The connection is bound to the workspace chosen at consent. | Reconnect deliberately and choose the correct workspace. | | Missing tool or refused action | Workspace feature, role/seat, host plan or app-only operation. | Check the limitation; perform app-only work in LeadKnight. | | Copy error | Clipboard access was denied or failed. | Select **Connector address** and copy manually. | | Unknown result after a change | The action may already have completed. | Inspect actual state before another instruction; avoid duplicate sends or publication. | ## Related pages - [Developers overview](https://docs.lead-knight.com/en/developers/overview/) - [Developer API — separate server-side integration](https://docs.lead-knight.com/en/developers/developer-api/) - [Upload photos and videos for the connector](https://docs.lead-knight.com/en/developers/connector-upload/) - [In-app AI assistant](https://docs.lead-knight.com/en/assistant/overview/) - [Workspace and team](https://docs.lead-knight.com/en/team/overview/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) --- # Upload photos and videos for the AI connector Use the connector upload link in the correct workspace, select or drop files, understand preparation and per-file results, and return to Claude or ChatGPT after upload. Canonical: https://docs.lead-knight.com/en/developers/connector-upload/ ## Availability and purpose > **Important:** The Claude/ChatGPT AI connector is **not available yet**. This workflow applies once the connector is turned on and you have a valid connection. The upload page is not a way to activate the connector. Use **Upload photos and videos** at `/connector-upload` to put files from your device into the LeadKnight workspace your connected app uses. After upload, return to Claude or ChatGPT so it can discover and use the staged media through the connector. Uploading alone does not create a campaign, attach a file to a post, authorize publication or send anything to recipients. This is different from uploading directly through the [Developer API](https://docs.lead-knight.com/en/developers/developer-api/), which uses a server-side bearer key and a multipart request. Do not paste an API key into this page or into the host conversation. ## Before you start - After the connector becomes available, finish [AI connector setup and consent](https://docs.lead-knight.com/en/developers/ai-connector/). Know which workspace was selected for the connection. - Sign in to LeadKnight with a current member of that workspace and have permission to upload media. An upload link is not permission to enter a workspace you do not belong to. - Ask the connected app for an upload link for your photos/videos. Use the link it provides so the intended workspace is included. - Keep the original files on your device. This is temporary staging for content creation, not a file backup or permanent hosting service. - Choose supported real image/video content, within the limits below after any image preparation. You must have permission to use the media. ## Open the correct workspace 1. Open the link from Claude or ChatGPT. The app route is `/connector-upload`; a supplied `workspace` query parameter identifies its requested workspace. 2. Wait while **Opening your workspace…** appears. If the requested workspace differs from the currently selected one, the page attempts to switch before accepting files. 3. If **Couldn't open that workspace.** appears, select **Try again**. Do not start another upload in a different workspace as a workaround. 4. If **You're not a member of that workspace.** appears, check the signed-in account and current membership. The page refuses invalid workspace IDs and workspaces not available to your identity. 5. Once **Upload photos and videos** is ready, check the workspace in the app shell before selecting files. If the URL has no workspace parameter, the page uses your current workspace rather than choosing the connector's binding for you. Changing the active workspace in the web app does not change the workspace selected for an existing AI connection. If they differ, use the upload link for the connection's workspace or reconnect deliberately through consent. Do not alter query parameters to try to bypass access restrictions. ## Choose files and follow the results 1. Under **Drop photos or videos here, or choose files.**, drag files into the drop area or use **Choose files**. You can select multiple files in one batch. 2. A row appears for each selected file, showing its name and **Waiting**. The batch is processed one file at a time; the current row changes to **Uploading…**. 3. If an image needs additional preparation, follow the compression decision described below. A skipped or failed file does not prevent later files in that batch from being attempted. 4. Watch each row for **Uploaded**, **Upload failed** or **Skipped**. Failed rows include a localized explanation when one is available. Do not assume all files succeeded because one row is uploaded. 5. Wait until the current batch is finished. **Choose files** is disabled while it is running; do not drop another batch during the upload. Once finished, you can choose another batch if needed. 6. When at least one file succeeded and processing has finished, a completion message states the number uploaded and asks you to return to Claude or ChatGPT and say **done**. The count reflects successful files still listed on this page, not failed/skipped files. 7. Return to the same host conversation and say **done**. Ask the app to use the uploaded files for the intended task. The page does not automatically navigate back or show asset IDs for manual copying. 8. Before any consequential action, review the requested content, account, destination and schedule. Upload completion itself is not permission to publish. File selection starts the upload workflow; there is no separate final upload or publish button. Keep the page open while processing. Do not reload it just to clear a waiting row, because the visible list is not a durable upload history. ### What each status means | Status | Meaning | What to do | | --- | --- | --- | | **Waiting** | The selected file has not reached its turn. | Wait while earlier files finish. | | **Uploading…** | The file is being prepared or uploaded; preparation can include a compression dialog. | Keep the page open and answer any visible preparation question. | | **Uploaded** | The upload request succeeded for that file. | Let the batch finish, then return to the connected app. | | **Upload failed** | Unsupported content, preparation refusal, server or connection failure. | Read the row's message, correct the cause and select the intended file again if appropriate. | | **Skipped** | Image preparation was declined/cancelled. | Select it again only if you want to approve preparation or supply a different version. | ## Formats, sizes and image preparation | File | Supported handling and limit | | --- | --- | | JPEG, PNG, WebP, GIF | Stored image formats; each uploaded image must fit within 10 MiB. Supported images already within the limit are sent as selected. | | Other image formats | The browser attempts conversion to a stored format if it can open the image. This is not a promise that every browser can open HEIC, HEIF, AVIF or every image file. | | MP4 video | Up to 256 MiB. Larger videos are refused before upload; this page does not compress video. | | Other videos or non-media files | The broad file-picker filter is not a guarantee of support. The supported video MIME is `video/mp4`; documents, audio-only files and unsupported video types are not accepted by this workflow. | ### Automatic preparation Oversized still images are re-saved on your device at reduced size/quality until they fit, when possible. A converted image can also have a different filename extension. If an unstored format can be opened by the browser, it is converted even if its original size was small. Conversion of animated AVIF keeps its first frame; do not rely on that format to preserve motion. If an image cannot be opened, save a copy as JPG or PNG and select that copy. A file extension or MIME label alone does not guarantee that the server accepts the actual file content. ### Manual compression or skipping If automatic preparation cannot fit a photo, **The image is too big** offers **Compress manually** or **Skip this image**. Manual compression can visibly reduce quality. For an oversized GIF, a warning explains that the animation will be lost and only its first frame is retained. 1. Read the filename, current size, upload limit and any animation warning. 2. Select **Compress manually** only if the quality/motion trade-off is acceptable. The prepared file continues to upload if it fits. 3. Select **Skip this image**, or dismiss the preparation question, to leave that file unuploaded. Its row becomes **Skipped**, and processing continues with the next file. 4. If even the stronger compression cannot fit the image, supply a smaller suitable copy instead of repeatedly selecting the same unmodified file. Keep your original if image fidelity or animation matters. A converted/uploaded still is not a replacement for the source video or animated image. ## Workspace changes, uncertain results and temporary storage The visible file list and counters reset when the active identity or workspace changes. The page stops continuing the old batch in the newly selected scope and does not send a prepared file into a different workspace after a preparation dialog. A request already in flight may already have stored a file in its original workspace; a cleared list does not prove it was cancelled or deleted. If you lose the completion screen or a network failure leaves an upload's outcome uncertain, return to the same connected workspace and ask the host to inspect available media before uploading again. Uploads have no exactly-once guarantee; repeating a file can create another asset. There is no per-row retry control: selecting a file again starts a new attempt. The completion message warns that files not used within 24 hours are removed. Treat that as temporary staging: unused files become eligible for cleanup after 24 hours, not a promise of deletion at the exact second. Ask the app to use/attach them promptly. Upload success alone does not attach the file to a campaign, and temporary media URLs are not permanent publication URLs. ## If something goes wrong | Symptom | Likely cause | What to do | | --- | --- | --- | | The connector cannot provide a usable journey | The AI connector is not available yet or not connected. | Wait for availability and complete connector consent; this upload page does not bypass it. | | Membership error | Wrong signed-in account, invalid workspace parameter or membership removed. | Use the right account and a workspace you currently belong to; request a fresh link from the intended connection. | | Workspace keeps opening or switching fails | The app has not reached the requested workspace. | Wait for readiness or select **Try again** after the switch error. Do not select files in a different workspace. | | Unsupported file message | The item is not a recognized image or MP4 video. | Supply a supported real media file; renaming an extension is not conversion. | | HEIC/other image cannot be opened | This browser cannot decode it. | Save/export as JPG or PNG and upload the copy. | | Photo too large after preparation | Compression could not fit it or was declined. | Use an appropriate smaller copy or deliberately approve the compression trade-off. | | Large video refused | The video exceeds 256 MiB. | Export a smaller MP4 outside this page, then select it. | | Some files succeed and others fail | Per-file results are independent. | Keep successes; correct only failed/skipped files instead of repeating the whole batch. | | Upload count/list disappears | Identity/workspace changed or page was reloaded. | Check media in the original workspace before uploading again; the list is not permanent history. | | Host cannot find uploaded files | Wrong workspace binding, no completed upload or unused staging expired. | Check the **Uploaded** rows and connection workspace, tell the host you are done, and inspect current media before retrying. | | Concern about accidental publication | Uploads stage media only, but later connector actions can act immediately. | Review the next instruction in the host; do not ask it to publish until content and destinations are confirmed. | ## Related pages - [AI connector availability, consent and disconnect](https://docs.lead-knight.com/en/developers/ai-connector/) - [Developers overview](https://docs.lead-knight.com/en/developers/overview/) - [Server-side Developer API uploads](https://docs.lead-knight.com/en/developers/developer-api/) - [Create a campaign manually](https://docs.lead-knight.com/en/campaigns/create-manual/) - [Workspace and team](https://docs.lead-knight.com/en/team/overview/) --- # Troubleshooting and support Find the right guide for sign-in, connections, publishing, AI, paid ads and developer integrations, and prepare a useful support request. Canonical: https://docs.lead-knight.com/en/troubleshooting/overview/ ## Start with the message on the screen A saved draft, an active campaign, a connected account and a published post are different things. Start with the exact message beside the item that needs attention rather than creating another campaign or connecting another account immediately. 1. Check that you are in the intended workspace. **Current workspace** and **Switch workspace** distinguish the workspace you are viewing. 2. Read the error or status on the affected campaign, connection, ad or assistant reply. 3. Use the matching guide below. Follow its prerequisites before trying the action again. 4. If the problem remains, contact support with the details listed at the end of this page. ## Find the right guide | What you are trying to do | Where to continue | |---|---| | Understand the app, its menus or initial setup | [App tour](https://docs.lead-knight.com/en/getting-started/app-tour/) and [onboarding](https://docs.lead-knight.com/en/getting-started/onboarding/) | | Create an account or finish email confirmation | [Create an account](https://docs.lead-knight.com/en/getting-started/create-account/) | | Sign in, change your password or manage your account | [Your account](https://docs.lead-knight.com/en/account/overview/) | | Find a workspace or understand team access | [Team and workspaces](https://docs.lead-knight.com/en/team/overview/) | | Connect a social account or reconnect an existing one | [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/) | | Choose Facebook groups or link a Facebook posting identity | [Connect Facebook groups](https://docs.lead-knight.com/en/channels/connect-facebook-groups/) | | Install, pair or troubleshoot the browser extension | [Install and pair the extension](https://docs.lead-knight.com/en/extension/install-and-pair/) | | Understand Facebook-group posting pace | [Posting presets](https://docs.lead-knight.com/en/extension/posting-presets/) | | Connect or sign in on a cloud phone | [Cloud phones](https://docs.lead-knight.com/en/cloud-phones/overview/) | | Understand why a campaign has not published yet | [Campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/) and [scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) | | Create content manually or with AI | [Manual campaigns](https://docs.lead-knight.com/en/campaigns/create-manual/) and [AI campaigns](https://docs.lead-knight.com/en/campaigns/create-with-ai/) | | Understand an assistant allowance message | [AI assistant](https://docs.lead-knight.com/en/assistant/overview/) | | Find expected scheduled content | [Calendar](https://docs.lead-knight.com/en/calendar/overview/) | | Find organic performance data | [Analytics](https://docs.lead-knight.com/en/analytics/overview/) | | Connect an advertising account or understand a paid-ad status | [Paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) | | Find a conversation | [Chats](https://docs.lead-knight.com/en/inbox/overview/) | | Add or find a contact | [Contacts](https://docs.lead-knight.com/en/contacts/overview/) and [add a contact](https://docs.lead-knight.com/en/contacts/add-contact/) | | Understand an audience | [Audiences](https://docs.lead-knight.com/en/audiences/overview/) | | Build a website or open a draft | [Sites](https://docs.lead-knight.com/en/sites/overview/) and [create a site](https://docs.lead-knight.com/en/sites/create-site/) | | Work on a picture or video | [Photo studio](https://docs.lead-knight.com/en/photo-studio/overview/) and [Video Studio](https://docs.lead-knight.com/en/video-studio/overview/) | | Understand plan or payment options | [Plans and billing](https://docs.lead-knight.com/en/billing/overview/) | | Set up an API integration or investigate an API error | [Developer API](https://docs.lead-knight.com/en/developers/developer-api/) | | Understand the planned Claude or ChatGPT connection | [AI connector](https://docs.lead-knight.com/en/developers/ai-connector/) | ## Common messages and first steps | Symptom | What it means or what to check | What to do | |---|---|---| | Sign-up email has not arrived | The confirmation screen does not prove that a new account was created for an already registered address. | Check spam and promotions. If the address already has an account, sign in instead. See [account creation](https://docs.lead-knight.com/en/getting-started/create-account/). | | Password-reset link is expired or already used | That link can no longer complete the reset. | Request a new link and use the latest email. See [your account](https://docs.lead-knight.com/en/account/overview/). | | A connection window never opens | Your browser may have blocked the popup. | Allow popups and retry the connection. See [connections](https://docs.lead-knight.com/en/channels/connect-social-accounts/). | | The extension accepted pairing but has not checked in | The connection is not yet ready for posting. | Make sure Chrome is open and follow [extension pairing](https://docs.lead-knight.com/en/extension/install-and-pair/). | | An AI allowance message appears | A usage limit can pause new requests even when an existing reply can finish. | Read the displayed availability time and use the [assistant guide](https://docs.lead-knight.com/en/assistant/overview/); repeatedly sending the prompt does not remove the limit. | | A tool or menu is missing | Availability and permissions can differ by workspace and feature. | Check the workspace first, then the relevant guide and your access with a workspace owner or admin. | | A paid ad is not delivering | Saving or checking a draft does not establish that the advertising platform is delivering it. | Review the ad status and any connection, approval or platform issue in [paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). | ## Contact support Email `contact@lead-knight.com`. Include: - The workspace name and the affected campaign, connection or page. - What you clicked, what you expected and what actually appeared. - The exact error text, the approximate time and your time zone. - Whether the problem occurs in the browser app, extension or an external AI client. - A screenshot with private details hidden, if it helps explain the problem. Do not send passwords, API keys, authorization headers, webhook secrets, pairing codes or login links. A screenshot of the message is safer than a screenshot of a credentials screen. ## Related pages - [Frequently asked questions](https://docs.lead-knight.com/en/troubleshooting/faq/) - [Getting started](https://docs.lead-knight.com/en/getting-started/overview/) - [Settings](https://docs.lead-knight.com/en/settings/overview/) - [Developer integrations](https://docs.lead-knight.com/en/developers/overview/) --- # Frequently asked questions Answers to common questions about languages, editions, connections, posting, AI allowances, account access, privacy and support. Canonical: https://docs.lead-knight.com/en/troubleshooting/faq/ ## Language, editions and access ### Can I use the app in English or Hebrew? Yes. The app has English and Hebrew interfaces, with right-to-left layout for Hebrew. Use the language control in the app header; in English, the switch to Hebrew is labeled **עברית**. See [the app tour](https://docs.lead-knight.com/en/getting-started/app-tour/). ### What is the difference between LeadKnight and Nadlanite? LeadKnight is the general-purpose edition. Nadlanite is the real-estate edition, with property-oriented wording and tools. Branding follows the workspace: the same concept may be called a campaign in one workspace and a property in another. See [getting started](https://docs.lead-knight.com/en/getting-started/overview/). ### Why can I not find a feature that another person can see? Check the current workspace and your permissions first. Some features are not enabled for every workspace. If you do not see a feature in the menu, it may not be enabled for your workspace yet; a missing menu item is not a reason to create a new account. See [settings](https://docs.lead-knight.com/en/settings/overview/) and [team access](https://docs.lead-knight.com/en/team/overview/). ### Why do my campaigns or connections seem to be missing? Make sure you are viewing the intended workspace. Use **Switch workspace** and check **Current workspace**. Content and permissions belong to a workspace, so switching workspaces can change what is shown. See [team and workspaces](https://docs.lead-knight.com/en/team/overview/). ## Connections and publishing ### Which social networks can I connect? The social-account catalog includes Facebook Pages, Instagram, TikTok, X, LinkedIn, YouTube, Pinterest, Google Business, Reddit and Threads. Availability depends on what is enabled for your workspace, and some integrations are beta; this list does not promise that every connection is available to you. Check the cards in **Connections** and follow [Connect social accounts](https://docs.lead-knight.com/en/channels/connect-social-accounts/). Facebook-group posting has its own [connection guide](https://docs.lead-knight.com/en/channels/connect-facebook-groups/), separate from ordinary social-account connections. ### Do all social networks require the Chrome extension? No. The browser extension is used for Facebook-group posting from your browser; other social-account connections use their platform connection flow. Facebook-group accounts can also have a cloud-phone publishing option where available. Follow [extension installation](https://docs.lead-knight.com/en/extension/install-and-pair/), [cloud phones](https://docs.lead-knight.com/en/cloud-phones/overview/) or [social-account connections](https://docs.lead-knight.com/en/channels/connect-social-accounts/) for the path you are using. ### Does Chrome have to stay open for Facebook-group posts? When the account uses **My browser only**, posts wait while the browser extension is offline. **Browser, cloud as backup** uses the browser first and needs a connected cloud phone for the backup rail. Do not assume a paired extension is online just because it was connected previously. See [the extension guide](https://docs.lead-knight.com/en/extension/overview/) and [cloud phones](https://docs.lead-knight.com/en/cloud-phones/overview/). ### Is there one fixed daily Facebook-group posting limit? No single number describes every profile. **Publishing settings** shows an estimate for that profile, with the selected pace, available groups and allowed parts of the day affecting the schedule. One publication means one post in one group, not one campaign. See [posting presets](https://docs.lead-knight.com/en/extension/posting-presets/). ### What do Safety, Balanced and Efficiency mean? They are the **Safety**, **Balanced** and **Efficiency** posting presets. LeadKnight's Safety preset uses trusted input events dispatched through the Chrome DevTools Protocol, which explains the extension's debugger permission, together with a humanized behavior model that other automatic posters do not use. No setting guarantees complete safety. Read [posting presets](https://docs.lead-knight.com/en/extension/posting-presets/) before changing the pace. ### Why has an active campaign not posted immediately? Check its schedule, selected destinations, posting identity and connection status on the [campaign board](https://docs.lead-knight.com/en/campaigns/campaign-board/). AI-created campaigns start paused: review the content before using **Resume all**. Group publishing also follows the profile's publishing settings: a paused profile does not publish until resumed. An active campaign is not a receipt proving that a particular post was sent. See [scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/) and [connections](https://docs.lead-knight.com/en/channels/overview/). ### Which time zone controls scheduled publishing? Scheduled campaigns use the workspace time zone. Check the time-zone information shown by the schedule rather than assuming it matches the device you are using. See [scheduling](https://docs.lead-knight.com/en/campaigns/scheduling/), [scheduled content](https://docs.lead-knight.com/en/calendar/overview/) and [settings](https://docs.lead-knight.com/en/settings/overview/). ### Where can I find planned content? Open **Scheduled content**. On the phone tab bar, its shorter English label is **Calendar**. Use the [calendar guide](https://docs.lead-knight.com/en/calendar/overview/) to distinguish planned content from content that has already gone out. ### Is chatting with the assistant on WhatsApp the same as sending WhatsApp campaigns? No. WhatsApp publishing and the assistant's WhatsApp connection are separate connections. Connecting one does not configure the other. See [the assistant](https://docs.lead-knight.com/en/assistant/overview/) and [connections](https://docs.lead-knight.com/en/channels/overview/); do not use an assistant conversation as proof that campaign sending is configured. ## AI and paid ads ### When does the AI allowance reset? The daily allowance resets at midnight in the workspace time zone. Interactive chats also have rolling three-hour budgets, so a daily reset and the end of a rolling limit are not necessarily the same event. Read the availability time shown with the limit message. See [the assistant guide](https://docs.lead-knight.com/en/assistant/overview/). ### Why can I reach the AI limit after only a few prompts? Usage is not counted only by the number of prompts you type. Token budgets account for provider input and output; outbound assistant messages, WhatsApp chunks and media count toward message budgets. Scheduled AI uses daily tokens, while interactive chats also use rolling budgets. The amount available depends on the applicable plan and usage rules; there is no universal prompt count. See [the assistant guide](https://docs.lead-knight.com/en/assistant/overview/). ### What should I do when the assistant asks for approval? Review the action and its details before using **Approve** or **Reject** on an **Approval needed** card. Do not approve an action just to dismiss the message. If the approval has expired, that card can no longer approve it. See [the assistant guide](https://docs.lead-knight.com/en/assistant/overview/). ### Is a saved or checked paid ad already spending money? Saving and checking are not the same as launching. Paid ads have their own publishing, approval and delivery statuses. Review those states rather than treating a draft preview as proof of delivery. Start with [paid ads](https://docs.lead-knight.com/en/paid-ads/overview/). ### Where should I look when an ad is not delivering or shows no spend? Use [paid ads](https://docs.lead-knight.com/en/paid-ads/overview/) to inspect the ad status, account connection and required approvals or platform issues. Organic content statistics and paid-ad results are different views; do not interpret organic analytics as an ad delivery report. See [analytics](https://docs.lead-knight.com/en/analytics/overview/). ## Sign-in and billing ### Why did I not receive the sign-up confirmation email? Check spam and promotions first. The confirmation screen deliberately covers both a new address and an address that may already be registered: if you already have an account, sign in instead. If the confirmation link has expired, sign up again to request a fresh one. See [create an account](https://docs.lead-knight.com/en/getting-started/create-account/). ### What if my password-reset link has expired? Use **Forgot password?** to request another link, then use the latest email. The app also provides **Send a new link** when a recovery link is expired or already used. See [your account](https://docs.lead-knight.com/en/account/overview/). ### I signed up with Google. Can I also use a password? Use **Continue with Google** to sign in, then set a password in **Settings**. The **Sign-in methods** section provides **Set or change password** and may ask you to confirm your identity. See [your account](https://docs.lead-knight.com/en/account/overview/). Do not create a second account just to add a password. ### Where do I find current plan and payment information? Use **Billing** and [the billing guide](https://docs.lead-knight.com/en/billing/overview/). Check the options and terms shown for your workspace instead of assuming a price, account allowance or payment arrangement from another workspace applies to you. ## Integrations, privacy and support ### Can I connect Claude or ChatGPT through the AI connector now? The AI connector is not available yet. [The AI connector guide](https://docs.lead-knight.com/en/developers/ai-connector/) describes the connection and consent flow for when it is turned on; it is not a promise of current availability. ### Can I put my Developer API key in browser code or share it with support? No. Treat the key as a credential for your server-side integration. Do not expose it in browser code, public repositories, screenshots or support requests. It acts within its workspace, scopes and your current permissions. See [Developer API](https://docs.lead-knight.com/en/developers/developer-api/). ### Where can I read about privacy and terms? Read the [Privacy Policy](https://lead-knight.com/privacy) and [Terms of Service](https://lead-knight.com/terms). They are also linked from sign-in and sign-up. For account-level questions, see [your account](https://docs.lead-knight.com/en/account/overview/); the FAQ is not a replacement for the legal policies. ### How do I contact support? Email `contact@lead-knight.com`. Include the workspace, the exact message, what you tried and when the issue happened. Do not include passwords, keys or login links. The [troubleshooting overview](https://docs.lead-knight.com/en/troubleshooting/overview/) has a checklist for preparing the request.