What This Guide Covers
The Credentials Module is where your organization checks members in at a convention, annual session, or other large meeting. It records who is present, tracks proxies and visitors, and produces the reports your credentials committee reads from the floor.
This guide is for parent group administrators. It covers one thing: how to give someone the access they need to work the credentials desk. It covers both patterns organizations actually use.
- A named person. A committee member or staff person who signs in as themselves.
- A shared desk account. One username and password used on every check-in laptop and tablet at the session, rotated every year.
If you are looking for how to run an event or check members in, read Set Up an Event and Check In Members with Credentials. This one is about access.
Before You Start
The Credentials Module is turned on for each organization on request. It is not on by default. If you do not see Credentials available in your system, contact Groupable support and ask to have it turned on for your group (the parent organization that oversees all locals, for example a state-level body or a national association). Only Groupable staff can turn it on.
You need administrator access to your group to follow this guide. The steps below involve assigning a user role, and that is limited to administrators.
A Credentials role has to exist before you can assign it. See Checking That the Credentials Role Exists below. This is worth checking first, because not every organization has one yet.
The ordering warning below applies to member and contact records only. If you are here for the shared desk account, the short way in Pattern 2 skips that problem entirely.
The One Thing Most People Get Wrong
The order of the steps matters, and doing them backward makes the system look broken.
When you open a brand-new contact record and look at the User Account panel, you will often see the word None and no way to invite anyone. Underneath, the panel still describes buttons called Send Password Reset, Resend Welcome Message, and Invite member to create account. None of them are on the screen.
That is not a broken screen. You cannot invite someone to create an account if they are not eligible for an account. A record is eligible when it is active, has an email address or phone number, and either holds a role (directly, or through an office) that allows a site account, or has a membership type that allows Connect access. A new contact has none of that yet. Assign the Credentials role first, and the Invite member to create account. link appears on the contact record right away.
So the order is always:
- Create the person or contact record.
- Assign the Credentials role.
- Return to the record, where the invite link now exists.
- Send the invitation and create the account.
Work in that order and everything below is straightforward.
Checking That the Credentials Role Exists
- From the main menu, click Admin, then click User Role Definitions.
- Look through the list for a role covering credentials access. Organizations name it differently, for example Credentials Check-In.
If you find it, open it with the edit icon and confirm three things:
| Setting | What it should be | Why it matters |
|---|---|---|
| Allows Site Account | Checked | Without this, nobody holding the role can be invited to create a login. This is the setting that makes the whole procedure work. |
| Assignable as Subordinate Role | Checked | Without this, the role does not appear in the list when you go to assign it on the Officers screen. The role also needs its Level set to Group, must not be marked Deprecated, and needs a Custom Identifier. Without the identifier, saving on the Officers screen fails with "Role can't be blank." |
| Credentials read and Credentials write | Both checked for a working desk role | Credentials read lets the account open events and reports. Credentials write adds everything else: creating, editing, closing, reopening, resetting, and deleting events, checking people in and removing check-ins, proxies, visitors, and Office Settings. Write without read gives no access at all. Someone who only needs to look at reports can have read alone. |
If no credentials role is in your list, contact Groupable support. Many organizations do not have one yet, and support can help you set it up. You can create one yourself if you have administrator access.
A note on what the role gives access to. The role you assign controls what the account can reach. A role whose only permissions are the credentials ones opens the Credentials Module. After signing in, the account also lands on the M2 home page, with a limited directory (locals, officers, and committees), limited member and local pages, and Connect if your group has it. It cannot edit members, see finances, or send mail. This is the reason a shared session login is defensible rather than reckless, and it is worth saying out loud to anyone who asks.
Pattern 1: Giving a Named Person Credentials Access
Use this when a specific person, such as a member of the credentials committee, works the desk under their own name.
Step 1: Assign the Credentials role
- From the main menu, click Group, then click Officers, then click Officers again. Your organization may label the first menu differently, for example Grand Lodge/Group.
- On the right side of the screen, find the Additional group users card.
- Click the green + icon in the corner of that card.
- In the Add Group User window that opens, type the person's name or member number in the search box. The results are grouped under Active and Inactive, and each one tells you what the match is, for example
Smith, Jane - R102106 - New Britain #0001 - Contact, so you can tell a contact from a member when you pick. - Choose the credentials role from the Role list.
- Add a note in Notes if it helps your successor understand why this person has access. This field is optional.
- Click Save.
The person now appears in the Additional group users list with their role beside their name.
Step 2: Invite them to create their login
If the person already signs in to your system, you are finished. The next time they sign in, they land in M2 and open Credentials from the apps icon, or from My Apps in the menu under their name.
If they have never had a login:
- Open their member record.
- Find the User Account panel.
- Click Invite member to create account.
This sends an email and a text message to the contact methods on their record, with a link to create their own username and password. They choose both. You never see or set their password.
Pattern 2: Setting Up a Shared Credentials Desk Account
This is the pattern most organizations run at a large session. One account signs in on every check-in laptop and tablet, so the people working the desk do not each need their own login and do not need to sign in and out as they rotate through shifts.
The account belongs to the office, not to a person. There are two ways to build it, and the first one is better for almost everybody.
The short way: an admin account
The Site Users screen says it plainly: administrative accounts are not tied to a membership and are generally used for group staff. A shared credentials desk login is exactly that. Built this way, the desk account needs no contact record, no member number, no mailbox, and no activation link, and you set and change its password yourself.
Step 1: Create the account
- From the main menu, click Admin, then click Admin Users.
- Click the green + icon in the corner of the Site Users card.
- On the Add Admin Account screen, fill in:
- First Name and Last Name. Use these to describe the desk, for example a first name of
Credentialsand a last name ofDesk. This is what appears in your user list. - Username. Something generic and boring.
credentialsdeskis a good choice. Usernames are 5 to 50 characters, with no spaces. - Password and Password Confirmation. At least 8 characters.
- First Name and Last Name. Use these to describe the desk, for example a first name of
- Click Create Site user.
The account is created and enabled immediately. Nothing is emailed and nothing needs activating.
Step 2: Give it credentials access
- On the account's screen, find the Permissions card.
- Click the green + icon.
- In the Add Permission window, choose your credentials role from the User role definition list, then choose your organization in the Group list. This list shows every group-level role that is not deprecated, so the role does not need Assignable as Subordinate Role here.
- Click Save.
The role appears in the Permissions table with a status of Active. Add nothing else. The whole point is that this login reaches the Credentials Module and nowhere else.
Step 3: Change the password when the session ends
- From the main menu, click Admin, then Admin Users, and open the desk account.
- Click the edit icon on the Site User card.
- On the Edit Account screen, type the new password in Password (Optional) and again in Password Confirmation.
- Click Save.
This is the part that makes the short way worth taking. An administrator changes the password directly, in about fifteen seconds, without needing access to anyone's mailbox.
The long way: a desk contact with a member record
Use this when you want the desk account to live on a contact record in your membership data, for example because your practice is that every login traces back to a record, or because you want the desk to appear in a roster.
It works, and the rest of this section walks through it. Be aware of the trade-off before you start: the Edit Account screen hides the password fields for any account tied to a membership. The annual rotation goes through Send Password Reset to the desk mailbox, through signing in as the desk account itself, or through an administrator using Become User (Step 6 below). If that sounds like more work than you want every year, use the short way above.
Step 1: Create the desk contact
Everyone in the system starts as a contact, whether or not they are a member. A desk account is no different.
- From the main menu, click Members/Contacts, then click Add. You can also reach this from the dashboard shortcut labeled Add a New Member/Person.
- On the Add Contact screen, fill in a name that describes the desk rather than a person. For example, a Last Name of
Grand Session Credentials Committee. - Under Organizational Information, pick a local (the individual unit within your organization, such as a lodge, chapter, or local committee) in the Local box. Start typing and choose from the list.
- Under Contact Info, enter an email address the office controls, such as a
credentials@mailbox. This matters more than it looks. The invitation and the account activation link both go to this address, and so does every future password reset. - Fill in the address and phone fields. State is required even though it is not marked with an asterisk. If you leave it blank, the form comes back with "State can't be blank" after you click Add.
- Click Add.
If the form comes back with an error, check the Local box before resubmitting. A failed validation clears your Local selection and resets it to Type Name, while the rest of the form keeps what you typed. Re-pick the local, then submit again.
The system generates a member number for the new contact, for example R102106. Write it down. You need it in Step 3.
Step 2: Assign the Credentials role to the desk contact
Follow the same steps as Pattern 1, Step 1 above. Search for the desk contact by the name you gave it. The search result labels it as a Contact, which is how you confirm you have picked the right record.
Step 3: Create the account
The desk contact is now eligible for a login, so the User Account panel on its record offers Invite member to create account. You have two ways to finish.
Option A, send the invitation. Click Invite member to create account. on the contact record. An email and a text message go to the contact methods on the record, and whoever opens that mailbox follows the link and sets the username and password.
Option B, create the account directly. If you would rather set the username and password yourself while you are sitting there:
- Sign out, or open a private browser window.
- Go to your organization's sign-in page and click Create your log in account.
- On the Create Your Account screen, enter the desk contact's member number in the Email or Member Number box. The hint on that screen describes member numbers as starting with a letter and being 7 characters long, which matches the number the system generated in Step 1.
- In Pick a username, enter something generic and boring.
credentialsdeskis a good choice. The username is free text, and you choose it here. - Enter a password twice. It needs at least 8 characters.
- Click Create Account.
Step 4: Activate the account
Either route ends the same way. Creating the account sends an email and a text message to the contact methods on the desk record, containing a link that activates the account. The account does not work until someone clicks that link.
This is why the email address in Step 1 matters. Someone in the office has to be able to open that mailbox. If the record carries a placeholder cell number, the text message goes nowhere useful, but the email is enough on its own.
If the message does not arrive within a few minutes, the activation screen has a Resend Welcome Message button.
Step 5: Distribute the login to the desk
Give the username and password to the people working the check-in stations, and sign in on each laptop and tablet before the session opens. Test one check-in before the doors open rather than at the doors.
Step 6: Change the password when the session ends
This step is not optional, and it is what makes a shared login acceptable.
Who: an administrator at the group level. When: right after the session ends and everyone at the desk has finished using it. Not next month, not before next year's session.
The Edit Account screen hides the password fields for an account built the long way. You have three routes instead:
Route A, send a reset. Use this route if the office controls the desk mailbox.
- Open the desk contact's record.
- Find the User Account panel.
- Click Send Password Reset.
A reset link goes to the contact methods on the record, so whoever opens the desk mailbox sets the new password.
Route B, sign in and change it. An account can always change its own password.
- Sign in as the desk account, using the password you are retiring.
- In the user menu, click My Account.
- Click the edit icon.
- Enter the new password in Password (Optional).
- Enter it again in the confirmation box, and save.
Route C, become the desk account. No mailbox and no old password are needed.
- As an administrator, open the desk contact's record.
- On the User Account panel, click Become User.
- In the user menu, click My Account.
- Click the edit icon.
- Enter the new password in Password (Optional).
- Enter it again in the confirmation box, and save.
Any route stops the old password working for new sign-ins. A laptop or tablet that is already signed in stays signed in until it goes unused for a month, so sign out of the desk account on every check-in device when the session ends. Next year's desk then starts from a password nobody from last year knows.
On changing the username too. Some organizations prefer to retire the username each year as well and create a fresh one. That works, and it is your choice. Rotating the password every year is the requirement. Rotating the username is a preference.
Removing Credentials Access
When someone leaves the credentials committee, remove their role rather than leaving it in place.
- From the main menu, click Group, then Officers, then Officers.
- In the Additional group users card, find their row.
- Click the delete icon at the end of the row.
Removing the role removes their credentials access the next time they sign in, or as soon as an administrator opens their member record. Open the record right after you remove the role so the change applies at once. If that was the only role giving them a login, their account no longer has anywhere to go.
For a shared desk admin account, open it under Admin, then Admin Users, and delete its credentials permission in the Permissions card. That takes effect at once.
Good to Know
- A contact is not a member. Adding a desk contact does not add anyone to your membership rolls, does not affect your counts, and does not create a dues obligation. It is a record that exists so an account can hang on it.
- The affirmation text. The User Account panel carries a line affirming that the individual asked you to send the communication. For a desk account there is no individual. What is happening is that an administrator is sending a message to a mailbox the office controls, which is the point of setting the account up that way.
- Read-only access is possible. A role with Credentials read but not Credentials write can open events and reports but cannot check anyone in or create an event. This is useful for a committee chair who wants to watch the numbers without touching the desk. The check-in screens still show the buttons to a read-only account, but the system refuses the change.
- An office can grant access too. Anyone holding an office whose role has Credentials read gets into the module.
- Access covers every event in your group. There is no way to limit a role to one local's events.
- A desk contact has to stay active. If the desk contact's status changes to inactive, its role stops granting access.
- A shared desk login with write can wipe an event. Write includes Reset and Delete, which remove every check-in on the event. Make sure the people at the desk know not to touch those buttons.
- You can undo most of this. Roles can be removed and passwords can be reset. There is no switch to disable an account; an account with no notes or emails attached can be deleted. Be careful about deleting a contact record after an account is attached to it.
- Admin accounts and member accounts behave differently on one point. An administrator can type a new password for an admin account on the Edit Account screen. For an account tied to a membership, those fields are not shown, and the password has to be reset by email, changed by the account itself, or changed by an administrator through Become User. This is the main practical reason to build a shared desk login as an admin account.
Troubleshooting
The User Account panel says "None" and offers no invite link. The person does not hold a role that permits a site account. Assign the credentials role on the Officers screen first, then come back. This is the most common confusion with this procedure, and it is covered in The One Thing Most People Get Wrong above.
The panel says the member is eligible for an account but has no phone or email address. The role is assigned correctly, but the record has no way to receive the invitation. Add an email address or a phone number to the record, then return to the panel and the invite link appears.
The credentials role is not in the Role list when I try to assign it. The role exists but is not marked Assignable as Subordinate Role, its Level is not Group, or it is marked Deprecated. An administrator can fix all three on the role under Admin, then User Role Definitions. If the save fails with "Role can't be blank," the role also needs a Custom Identifier. If there is no credentials role in that list at all, contact Groupable support.
"State can't be blank" after submitting the Add Contact form. State is required on that form even though it carries no asterisk. Fill it in. Check the Local box as well before you resubmit, because a failed validation clears it.
The activation message never arrived. Check the email address and phone number on the contact record. Then use Resend Welcome Message, which appears on the activation screen and on the User Account panel for an account that has not yet been enabled.
"You already have an account awaiting activation." The account was created but never activated. Follow the resend link on that screen to send a fresh activation message.
Someone still has credentials access after the session. That is expected. Roles do not expire on their own. Remove the role when the person leaves the committee, and change the shared password when the session ends.
Glossary
Group: The parent organization that oversees all locals, districts, and regions. Examples include a state-level governing body, a national association, or a political party.
Local: An individual unit within your organization where members hold their primary membership. Depending on your organization, this might correspond to a lodge, chapter, local committee, or similar body.
Member: A person who holds membership in your group.
Contact: A person or entity in your records who is not a member. Everyone added to the system starts as a contact. A shared credentials desk account lives on a contact record.
Role: A named set of permissions. Assigning a role to someone determines which parts of the system they can open and what they can change there.
Additional group users: The card on the group Officers screen where you give someone a role that is not tied to an elected or appointed office. Credentials access is assigned here.
Site account: A username and password that signs in to your system. A person can hold a role without having a site account, and a role has to permit a site account before anyone holding it can be invited to create one.