Skip to content

Settings, members, and roles

Every panel in Settings, plus how to add colleagues and what each role can do.

Dashboard → Settings is a single page of panels. The header shows your subdomain and your did:web identifier, and a row of jump links takes you to any section: Plan & billing, Organization profile, Domain verification, Organization logo, Members, Sub-organizations, API access, Webhooks (admins only), Email preferences and, for admins, the Activity log.

Plan & billing
Your plan, usage against your annual limit, and the link to the billing portal. See Plans and billing.
Organization profile
Your organization's display name, website and optional LinkedIn page ID. Admins only. The website, if you give one, must be a full address such as https://www.university.edu. A bare name like university.edu is refused with a message, and what you typed is kept.
Domain verification
Confirm your email domain. See Confirming your domain.
Organization logo
Upload the logo shown on your public organization page. See Branding.
Members
Invite colleagues with a role and, if you use sub-organizations, an access setting; change them later; resend or withdraw invitations.
Sub-organizations
Create and remove schools, departments, or programs. See Sub-organizations.
API access
Create and revoke API keys. Enterprise only — see API.
Webhooks
Admins only. Signed requests to your own server when awards change. Enterprise only — see API.
Activity log
Admins only, on its own page (Settings → Activity log). One row for each recorded action in your organization: who did it, when (times are UTC), a plain sentence about what happened, and the badge or sub-organization it concerned. It covers awards issued, revoked and restored; badges moved, copied, filed or given a new graphic; member invitations, role changes and removals; settings, API key and webhook changes; and single sign-on sign-ins. Filter by kind of event, date range or badge name, then Export CSV for the same filtered list. When an Incredify operator acts on your account, for example during a support session you asked for, the row appears as "Incredify operator". Recipients' email addresses are never shown or exported. Rows cannot be edited or deleted, and nothing removes them automatically: they are kept for as long as your organization exists. Three limits to know before an audit: creating, editing, archiving or deleting a badge is not logged (once a badge has an award its name, description, criteria and skills cannot be edited at all); a row is written just after the action, so if that write fails the action still stands and the row is missing; and a member who has since been removed appears as "Former member". The recipients export and the full JSON export do not say which member issued or revoked an award: only this log does.
Email preferences
Your own opt-in for onboarding tips and the monthly summary. See Emails we send.

Adding a member

No account needed

Enter your colleague's email address and choose a role. If your organization has sub-organizations, choose their Access too: All badges, or one sub-organization. It takes effect when they accept, and the invitation names it. Admins always have access to all badges, so the choice is ignored for them. We email them an invitation. They sign in at the login page with that address, using the one-time code we email them, and choose Accept; only then do they become a member. If your organization uses single sign-on, signing in through it also accepts the invitation. Until they accept, admins see them in the list as Invited, with their role and access, which can't be changed until they join. If they lost the email, use Resend on their row (a few times a day at most); Withdraw cancels the invitation and asks you to confirm first. An invitation lapses 14 days after it was sent: it shows as Lapsed and can no longer be accepted or resent, and it is then removed from the list; to try again, invite them again. You get the same answer whether or not the address already has an Incredify account. Someone who already belongs to another organization can be invited, but can't accept until they leave it (their own Leave this organization link). Inviting an address that already has an open invitation from your organization is refused; use Resend instead. Promoting an issuer to admin clears their sub-organization access, since admins see everything.

The invitation email links to the sign-in page. After signing in they see the invitation with Accept and Decline; nothing changes unless they accept, and they can set up their own organization instead. A member who wants to go can use Leave this organization at the bottom of the Members panel; the only admin of an organization can't leave until another admin exists.

Roles

AdminIssuer
Design badgesYesYes
Issue badgesYesYes
Revoke and restore badgesYesNo
View recipients and exportYesYes
Create pathwaysYesYes
Add and remove membersYesNo
Manage sub-organizationsYesNo
Move or copy badges between sub-organizationsYesNo
Organization profile, logo, verificationYesNo
Billing and plan changesYesNo
API keysYesNo

You can't lock yourself out

The last remaining admin can't be demoted or removed. Promote someone else first.

An issuer assigned to a sub-organization sees only that sub-organization's badges and awards, plus any organization-wide badge and its awards. An unassigned issuer sees everything organization-wide. See Sub-organizations.

Related

Still stuck?

Email us at hello@incredify.net — a human will answer.