Table of Contents

How do roles work?

Kate Santo Updated by Kate Santo

In a padoq, personas can have different roles assigned to them: guest, member and admin. Depending on the role, the persona will experience padoqs differently.

Find out more about roles in this guide.

See for yourself

  • You can download the iOS or Android app on your phone to follow this journey along. And you can also log in or sign up to the web app here
  • You can also follow along by checking out the images or code snippets in this guide
  • And you will find the relevant endpoints linked and explained in this guide, but the full API is documented in Swagger UI

Admins

By default, the user who creates a padoq becomes the padoq admin. The admin can then make other members of the padoq admins too. The admin role is defined by these traits:

  • Admins can create these types of posts in a padoq: basic, comment, survey, payment_rq, event, form, template, note, reminder and vote. This is the default list, and it's stored in our API, so it's not editable through the UI. Find out more about post types overall in our guide: Post types
  • Admins are able to manage every editable aspect of a padoq. Find out more in Managing a padoq
  • Admins are notified about membership requests and have the ability to approve or reject them. Find out more in Explore - The user requests to join a padoq
  • An admin is also a member of their padoq. When they create a post, for example, they can choose to create it as the admin or as a member

Guests and members

Guests and members have a different set of permissions in a padoq. Find out the main differences below.

Permitted post types

In a padoq, guests and members have different permissions when it comes to posting. For example, the permittedPostTypes and guestPermittedPostTypes properties in a padoq define the types of posts that members and guests can create, respectively.

There isn't a default list of posts that guests can create. Instead, app owners decide on this. However, in standard padoqs, the array of permittedPostTypes for members will have this content by default:

  "permittedPostTypes":[
"BASIC",
"COMMENT",
"VOTE",
"VOTE_RS",
"PAYMENT_RS",
"EVENT_RS",
"SURVEY_RS",
"FORM_RS"
]

Admins have the choice of adding post types to this array via an option in the UI. Commonly, admins can allow members to create events and surveys, not only event responses and survey responses. Find out more about post types overall in our guide: Post types.

Accessing content

In a padoq, guests and members have access to different content. For apps that allow guests, the user will see everything that has been made available for guests in a padoq. That's posts where the recipientRoles property has a value of guest.

For example, for apps that have paid subscriptions, the padoq admin might set up a few posts that guests can see, including a post to pay for a subscription. When they subscribe, they will have access to all of the posts where the recipientRoles property has a value of member.

It's important to note that a namespace might allow guest access, but not all padoqs need to split their content for different roles. In a namespace that allows guest access, users can find padoqs that are public and that require no subscription to view its full content.

How did we do?

User profile

App menus

Contact