Documentation/Studio
Back
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
  • Registers
    • Create and change a register
    • Upload and download entries
    • Add, edit and deactivate entries
    • Groups
    • Challenge codes
    • Connect and test an external register
    • Register activity
  • Membership definition
    • Add and order register assignments
    • Filters and outcomes
    • Preview and test before saving
    • Save and version history
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
  • Frontends
    • Create a frontend
    • Frontend keys
    • Sign-in settings
    • Sign-in branding
  • Login with appsolut
    • Sign-up and onboarding
    • Sign-in and sign-out
    • Support requests
  • Frontend users
    • Find a frontend user
    • Membership and activations
    • Block a frontend user
    • Export a frontend user's data
    • Disconnect a frontend
  • Membership check
    • Check modes
    • Results and the check log
    • Rate limits
    • Grace rule
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Billing
    • Roadmap and feature requests

Create a frontend

Add a website or app, choose the community that serves it and decide whether membership is mandatory.

Studio roles: "Owner", "Administrator" and "Frontend manager".

Every frontend needs a community, so create the community first. Without one, the dialog says "A community is needed first" and, if your Studio role allows it, links to "Communities".

Create a frontend

  1. Open "Frontends" in the sidebar.
  2. Choose "New frontend".
  3. Enter the "Name", for example "Pannoniqa Portal". Frontend users see this name on the sign-in screens, so use the name they know.
  4. Under "Kind", choose "Internal" for a website or mobile app of your own, or "External" for an app of someone else that you connect. You cannot change the kind later.
  5. Under "Community", choose the community that may use the frontend, for example "All staff".
  6. Leave "Membership mandatory" on if only members of that community may use the frontend. Switch it off if anyone with an account may sign in.
  7. Choose "Create frontend".

The frontend appears in the list with its "Kind", "Community", "Membership" ("Mandatory" or "Optional") and its "Active keys". Choose its name to open it.

The page of the Pannoniqa Portal with the Settings, Keys, Sign-in and Disconnect frontend cardsThe page of the Pannoniqa Portal with the Settings, Keys, Sign-in and Disconnect frontend cards

Change the name, community or membership rule

  1. Open the frontend.
  2. Under "Settings", change the "Name", the "Community" or "Membership mandatory".
  3. Choose "Save changes".

If you change the community or the membership rule, the Studio asks you to confirm: "This changes who may use the frontend". From the moment you save, the new rule decides who may use the frontend, and frontend users who no longer qualify cannot use it any more.

Two frontends of one organisation cannot have the same name.

Next steps

  • If the frontend's backend calls the Studio, issue a frontend key.
  • To sign users in with Login with appsolut, set up the sign-in settings.