Who is Padoq?
How to Submit Your App
How to Submit Your App to the Google Play Store
Google Play Console: How to push an update live
App Store Connect: How to push an update live
How to Submit Your App to the App Store
App Listing Design Requirements
Setting up Test Users
The Super Admin Dashboard
Setting up a merchant account
Managing group members
Types of Groups
Adding tags to Groups
Update your Profile in a Group
Leaving a Group
Managing and deleting your group
What is a Padoq (or Group)?
Group Privacy Settings
Group Tile Menus
Types of Posts
Edit or Delete Posts
Share a Post
Boost a Post
Report a Post
Creating a Poll
Creating Payment Posts
Filtering and Sorting Posts
Copy a Post
Posting to Select Recipients
Your notifications and activity
3rd Party Tools
Firebase Cloud Messaging
Setting up a SendGrid account
Third Party Tools - End User data collection
Help! It won't let me log in
How do I Report an Issue?
What platforms is the app available on?
The Padoq platform
User registration (onboarding)
How do roles work?
Primary app menu
Padoq feed and menus
Creating a padoq (group)
Managing a padoq
What are Padoq categories?
Verified by Padoq
Notifications and activity
Super Admin Dashboard - Issue reports
Create and Manage Forms (Information Collection)
Glossary | A guide to how we talk
Updated by Kate Santo
This is a glossary for all of us to use, discuss and build. If there's a term that confuses you, your colleagues, customers or users, let us know and let's explain it here 😊
An admin is a user with more privileges in a group than what a group member would have. An admin is typically the persona who can edit group settings, remove personas from the group, delete the group, etc.
Literally, bopad is padoq upside down. It means exactly the same as Your Own App. Internally, we'll often say bopad because it's kind of easier to pronounce. But let's not confuse clients by using this term when we communicate with them.
A group is a defined section in Your Own App / a bopad. A group is the same as a padoq, but in client-facing comms, we should always say group, not padoq, as clients don't see the word 'padoq' in their apps.
Depending on what a client's app is for and how their business is structured, groups can be called different things:
But the reality is that, whatever they are called in each client's app, groups work the same way deep down and have the same or very similar functionalities. Groups can be customised in different ways. Find out more about this in Creating a padoq (group) or in Managing a padoq.
A namespace is an app's unique name.
Ops or Operations
A user with enhanced privileges. In Swagger, you might see "Ops" or "SysOps" when an action requires enhanced privileges to be performed.
Padoq: the name of our company.
Padoq: the name of the free app you can download on your App Store or Play Store, or you can access the web version here.
A padoq: a defined group in the free Padoq app. For example Books, Manchester Business Networking, etc. See 'Group'.
A padoq: internally, a padoq is also a defined group in Your Own App. But in client-facing comms, we say group instead, as clients don't see the word 'padoq' in their apps. See 'Group'.
Each namespace and each user lives in a defined part of our system. Each of those defined parts is a partition.
A user's alias in a padoq or group. Separating users from personas allows for greater protection of the user's identity and privacy. For example, group admins can only see personas, but they can't see the real user's information.
A space in the web app that allows additional settings for a group. Read more in Super Admin Dashboard.
A user in one of our apps. Different from "persona".
Your Own App (YOA)
This how we call an app we build for a client. This is the term our client will see in their contract -so why not use it in client-facing comms? 🤜 🤛
Some examples of Your Own App are the Quintain Living app and the UK IT Leaders app.