The create invite code form currently has an initial value for Roles set to 'member'. There are currently four roles for which an invite code can be issued: 'admin', 'staff', 'member', and 'coach'. When another role is entered, and the user clicks CREATE , the Roles input value will show 'member' again, which may cause confusion for the user creating the invite code.
Invite code with 'staff' role invited:
Upon clicking CREATE, 'member' (the initial state for the form Roles field) will reappear, which may make it unclear as to what role an invite code was created:
A number of strategies may be employed, the simplest seeming to be making sure the new value remains when clicking CREATE. Another strategy involves implementing a dropdown menu (similar to the Timezone field in the create chapter view (chapter form)). Additionally, the Invite Codes list in the edit chapter view (chapter form) could be modified to show the role information.
The create invite code form currently has an initial value for
Rolesset to 'member'. There are currently four roles for which an invite code can be issued: 'admin', 'staff', 'member', and 'coach'. When another role is entered, and the user clicksCREATE, theRolesinput value will show 'member' again, which may cause confusion for the user creating the invite code.Invite code with 'staff' role invited:
Upon clicking
CREATE, 'member' (the initial state for the formRolesfield) will reappear, which may make it unclear as to what role an invite code was created:A number of strategies may be employed, the simplest seeming to be making sure the new value remains when clicking
CREATE. Another strategy involves implementing a dropdown menu (similar to theTimezonefield in the create chapter view (chapter form)). Additionally, theInvite Codeslist in the edit chapter view (chapter form) could be modified to show the role information.