Signing in and account access

Signed-out visitors can use the intro page and sign-in entry. Use the authentication options actually displayed on the sign-in screen; this manual does not guarantee any provider is enabled. Make sure you use the same sign-in identity as your ShootFeed account. If you cannot sign in, use the public Contact form to reach support and receive updates at the email you provide. Never send passwords, recovery codes, service keys or session cookies. Account merges, ownership changes and suspicious access require owner review rather than an automatic answer.

Visiting the root home address while signed out opens the intro page rather than forcing the login screen. An eligible signed-in user normally goes directly to the main dashboard grid; access or agreement requirements may still need completion. This explains routing, not the current visitor's authenticated state.

## Join Beta applications

Public visitors who select Join beta are taken to `/beta-apply`, not directly to account creation. ShootFeed is accepting a small number of content creators during the private beta. Required fields are marked with an asterisk. The form starts with a Full name (first and last) and email address, then asks how many social accounts the creator actively manages and requires an acknowledgement that they can spend about 30 minutes each week testing and sharing candid feedback. It then collects at least one social-media username or profile link, Instagram account type and Facebook personal profile/Page setup details, current and desired Posting rhythm, a required Scheduling software experience choice, and a nonempty Tell us about your workflow note. The workflow prompt asks what they create, which accounts they manage, and how ShootFeed could help; any nonempty answer is accepted. Apply remains clickable so missing information produces visible validation. The scheduling question distinguishes current users, people who have used the tools before, and people who have not used them; naming tools is optional. After submission, the applicant sees an on-screen receipt with a reference number and receives an email confirming that the application is under review.

The ShootFeed owner reviews applications in Settings → Admin → Customers. Approve starts app access immediately; Instagram, Facebook and Threads tester invitations are separate and do not block app login. Wait for the access-ready email, use the matching email address to sign in, and accept the beta agreement. This email confirms 90 complimentary days, no payment information and no automatic charge. Getting started guides profile grouping, account connections, posting days and times, caption defaults and the first draft. One ShootFeed profile can group the platforms for the same person or brand.

The owner can record an additional requested Meta account using Add requested account on an approved application. Each new Tester grant needs a separate, exact-account Maverick confirmation; this does not approve a new applicant or grant Administrator or Developer access.

The owner tracks Instagram, Facebook and Threads independently as Invitation needed, Waiting for tester, Ready to connect, Connected or Needs attention. Each platform gets a short instruction email after its invitation is verified sent. App access, invitation acceptance and a connected publishing account are distinct. Testers accept their own invitations and provider permissions. In Getting started, Your beta accounts shows their own account setup and platform instructions; Refresh setup checks the recorded status. A pending platform invitation lets them continue setting up ShootFeed.

Instagram needs a professional Creator or Business account; a linked Facebook Page is not required. Accept ShootFeed in Instagram's Website permissions → Apps and websites → Tester invites (menu labels can vary), then Connect in Profiles. For Facebook, open Apps and websites in Safari or a desktop browser signed into the invited personal profile, scroll to Requests, and accept ShootFeed. No developer registration is needed. The Facebook app can use a different login session. In ShootFeed, add the managed Facebook Page, rather than the personal profile, and connect using the account that manages it. For Threads comment replies, open Threads → Settings → Account → Website permissions → Invites, accept ShootFeed, then use Allow comment access if a ShootFeed notification or Engagement warning reports missing reply permissions. Ordinary Threads publishing uses Connect separately.

At roughly day 60, ShootFeed emails a reminder with the complimentary period's recorded end date; future continuation choices are explained before access changes. Not right now sends a courteous waitlist message. An email queued for sending is not a delivery confirmation. If app access or an invitation needs attention, contact support without sending passwords or authorization links.

TikTok controls and platform choices are hidden from beta users and the public until approval; private TikTok setup and publishing remain available only to the ShootFeed owner. Do not suggest those owner-only controls to ordinary users.

The owner’s access-ready email confirms ShootFeed login access, not completed Meta connections. Admin tracks tester invitation, acceptance and connection separately for every requested account. Approved Instagram or Threads profile URLs and an exact Facebook personal profile.php?id= reference can be resolved for tester setup without changing the owner’s recorded approval. Ambiguous names, Facebook Page links and unrelated URLs require clarification.

The application visibly lists the platforms currently available to beta users, including Threads and YouTube. Add every exact account you want to test, including multiple accounts on one platform. For YouTube, enter a channel URL or @handle. The managing Google login is chosen during the normal Google authorization flow; the early-access application does not require it. Other platforms may be requested as interest without enabling unavailable integrations. Invitation instructions are emailed once per exact verified Meta account after the invitation is sent, not merely when the application is approved. YouTube connects directly in Profiles once ShootFeed app access is enabled. No separate YouTube request, acceptance, Google test-user invitation or connection-ready email is needed.

When a tester’s acceptance is recorded, ShootFeed queues one next-step email for that exact account, explaining how to connect it (or enable Threads reply access). A queued acceptance email is superseded if the role is already accepted, so testers receive the current action rather than outdated instructions. Repeated scans do not resend the same step. A successful ShootFeed login is not treated as a completed platform connection.