Lock your app from unwanted visitors

Locking & Restricting Access in Your Onespot App

While anyone can download your Onespot app, you can restrict access to certain features or content using privacy settings. There are two main ways to lock your app—making the entire app private or locking specific account types with passcodes.


Option 1: Locking the Entire App


🔹 Best for: Schools that want to restrict all content from public users.

🔹 How it works: Users must enter a passcode before they can join or access anything in the app.


How to Lock Your Entire App:

  1. Open the Onespot Admin Panel.
  2. Click the Lightning Bolt Icon → Publishing & Privacy.
  3. Select “Lock App & Make it Private”.
  4. Enter a passcode that users must enter upon joining.
  5. Changes will Autosave—Now, only users with the passcode can proceed.

📌 Downside? This method locks the entire app, which may not be ideal if you want visitors to access general school info.


Option 2: Locking Specific Account Types (Recommended)


🔹 Best for: Schools that want visitors to access some content but restrict certain roles (e.g., parents, staff).

🔹 How it works: The app is open, but specific user roles require a passcode to access their assigned content.


How to Lock by Account Type:

  1. Open Onespot Admin Panel.
  2. Click Lightning Bolt → Account Types.
  3. Find the account type you want to lock (e.g., Parents, Staff).
  4. Add a passcode for that role.
  5. Changes will Autosave—Now, only users with the passcode can sign up as a specific role.

📌 Example:

  • Visitors can access public info like news & events.
  • Parents & Staff must enter a passcode to unlock private resources like class directories & internal documents.

Why Use This Feature?

Locking specific account types ensures that sensitive school data stays private, while still allowing public-facing content to remain accessible. It gives parents and staff secure access to the tools they need without making the entire app inaccessible. 🚀

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.