Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does a site restrict membership registration to certain people? #60

Closed
stuartpb opened this issue Jan 26, 2016 · 7 comments
Closed

Does a site restrict membership registration to certain people? #60

stuartpb opened this issue Jan 26, 2016 · 7 comments

Comments

@stuartpb
Copy link
Member

For instance, a government site for Seattle residents.

This will be important when organizing regular reviews for sites like this, as only certain people will be able to review sites like this, and it'd be nice to let them know about restrictions like this up front, before they go opening a tab for a site they're not eligible for an account on.

@stuartpb stuartpb added this to the future milestone Jan 26, 2016
@stuartpb
Copy link
Member Author

stuartpb commented Mar 9, 2016

CenturyLink limits accounts to CenturyLink customers, and deletes them if you discontinue service.

@stuartpb
Copy link
Member Author

In this same vein, there should maybe be values for what extent a site requires accounts: is there private content? Is there public content? Is there only a certain amount of participation allowed without an account?

This part should maybe get its own issue, and definitely requires practical use cases to guide its structure.

@stuartpb
Copy link
Member Author

This is also sort of convergent with #6, since this can be in the form of a "profile field" that you have to fill out where the data has to come from an account you set up outside (or something like that, like your driver's license number).

@stuartpb
Copy link
Member Author

stuartpb commented Feb 9, 2017

I'm thinking any concern that's citizenship-based can use the address structure you see in systems like Google Places, where it's "COUNTRY", followed by "ADMINISTRATIVE AREA LEVEL ONE", then "ADMINISTRATIVE AREA LEVEL TWO", then "CITY", etc, since that seems to be an extensibly- and extensively-vetted standard suitable for global use.

@stuartpb
Copy link
Member Author

stuartpb commented Feb 9, 2017

Other such concerns:

  • Customer of the company
  • Customer of another company (thirdparty?)
  • User account present on another site (this definitely sounds like overlap with thirdparty, and especially thirdparty.auth.domains)
  • Resident of a property (activebuilding, for instance)
  • Employee of the company (though I wouldn't put this, for, say, Slack, since while that might be a principle for some Slacks, it's not a guaranteed limit for all of them, the way it would need to be to be an obstacle to profiling)
  • Money stuff (Profiling money handling #161)

@stuartpb
Copy link
Member Author

stuartpb commented Feb 9, 2017

Note that both ResidentPortal and ActiveBuilding have demo as a subdomain that the public can use to try their platform, which doesn't require this. It might be looking into documenting if there's a way to do this for sites that have requirements like this, at least somewhere like a wiki page.

@stuartpb
Copy link
Member Author

Moving discussion to #27 per #308

@opws opws locked and limited conversation to collaborators Sep 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant