define requirements for user management

[xmatthewx]

What does the badgeKit interface require to facilitate user management?

[xmatthewx]

@threeqube and @iamjessklein -- see @brianloveswords description of systems (cities), issuers, programs, https://github.com/mozilla/badgekit-issue/issues/2

[threeqube]

@xmatthewx not very clear on what this ticket is addressing. Who is the "user" here?

[xmatthewx]

Manage Users with permission to log into to BadgeKit.

ex: A system (city) admin creates user accounts for program admins etc. What's required to smoothly manage all those users? And set their permissions to create programs, issue badges, review evidence, and give other users permissions?

Currently in badger.openbadges you see the screenshot below. Is this all that's required?

[threeqube]

Thanks @xmatthewx that helps.

So far from open badger perspective, we have 3 different kinds of users:

• omnipotent admin: anyone with a @mozillafoundation.org email address
• issuer admin: can create and edit badges, issue badges, create claim codex
• access list admin: can only generate claim codes and issue badges

We didn't have issues during CSOL with these roles and tiered access privileges.

[iamjessklein]

I'm interested in some different scenarios; settings:

• who can draft badges?
• who can evaluate badges?
• who can publish badges?
• who has admin privleges?
• are we giving privileges universally, or are we interested in making privileges specific to a single badge, a group of badges or a program?

[carlacasilli]

I began to work through some of this a while back on this etherpad: https://openbadges.etherpad.mozilla.org/carla-badgekit-list Take a look at the content there (sort of a mental data dump of system design roles) because there are a lot of subtle distinctions in there that can help to inform where this heads.

[xmatthewx]

thanks @carlacasilli this is extremely helpful

everyone can also contribute thoughts here: https://openbadges.etherpad.mozilla.org/badgekit-accountsettings

[iamjessklein]

I edited the account settings etherpad and would like to get to some general level of agreement on these as well as clarity on the requirements for account settings and preferences for the March 2013 release.

https://openbadges.etherpad.mozilla.org/badgekit-accountsettings

[iamjessklein]

Here are the proposed account settings (note where I have indicated that something is MVP):

Account Permissions:

• An admin can give other users different kinds of editing, viewing and sharing privledges.
• Add user, then click on which permissions to give them:
  • edit badge content
  • publish badge content
  • read badge content
  • assess
  • define requirements
  • define / modify rubrics
  • define badge issue thresholds:
    • e.g. if 2 out of 3 requirements/rubrics are met, issue badge
  • define pre-canned messages for < 13 badge earner feedback
  • define acceptable media for badge evidence
  • issue

Sharing settings: (this is ilke in dropbox having shared folders/shared files)

• BadgeKit shared programs let you collaborate on a set of programs. When someone joins a shared program, the program appears inside their dashboard. Program name invite user to shared program *MVP suggestion= give users overall access to all the programs
  • BadgeKit shared Badges: not copy, but share permission to issue same exact instance

Account Settings:

• An individual user (admin or user) can adjust their personal settings and preferences *As a user, I can define:
  • Name:
  • Username (?)
  • E-mail:
  • SMS
  • Networks
  • Language
  • Login Notifications: Enabled
  • Trusted Contacts:

Privacy Settings: - not in MVP?

• Who can see my stuff?
• Who can contact me?
• Who can look me up?
• Who can access and use my data?

Notification Settings:

• How you get notifications:
  • E-mail
  • Push notifications
  • Text
• Daily digests: Enabled

Program & Badge Settings

• Name
• Postal Address
• Web Address
• Email
• default cc license

[threeqube]

:+1: pending @cmcavoy thoughts on

Sharing settings: (this is ilke in dropbox having shared folders/shared files)

and

Privacy Settings: - not in MVP?

[cmcavoy]

Generally :thumbsup:, everything here is good. That said, for now - I think we should stick with broader access controls: a user associated with an issuer has access to edit that issuer's badges.

I'd like to start broad and simple with access, and then narrow it down after we're sure we have a usable product. If this becomes a blocker, where we absolutely have to have fine grained controls to release, then we can revisit.

[iamjessklein]

Added to wiki: https://github.com/mozilla/openbadges-badgekit/wiki/User-Settings---Requirements

Closing this issue.