Sign-in
Accounts, and what each person is allowed to do.
People sign in as themselves, and what they can see follows from who they are. That is one decision — who may have an account — and a set of consequences that reaches every page, because every screen then has to answer whether this person is allowed to be on it.
What we need from you
- Who may create an account, and whether they may do it themselves
Open registration, invitation only, or created by an administrator. Each is a different amount of work and a different amount of risk to carry afterwards.
- What each kind of person is allowed to see and change
Written per role rather than per person, because people move between roles and the permissions have to follow the role rather than the name.
- What should happen to an account when somebody leaves
Disabled, deleted, or handed to somebody else — and what becomes of the records they created. Far easier to answer before the first person leaves than after.
What is true once it is in
- People seeing their own information and nobody else's
Enforced on the server for every request, rather than by which links happen to be shown on the page.
- Access removed by your team rather than by a developer
From an administrative screen, so revoking somebody's access is immediate rather than a support request that waits its turn.
- A record of who changed what, and when
Which is what makes a disagreement about what happened answerable rather than a matter of whose memory is better.
Fun fact
Computing’s first passwords were written for MIT’s Compatible Time-Sharing System in the early 1960s, and they were kept in a plain file any user could print. In 1962 a researcher did exactly that to get more time on the machine.
The other connections
Get in touch
Every one of these reaches us directly, and is answered by a person.
A new project, a quote, or a question about one that is running.
- Reaches us at
- +355 69 752 2209
- Carries
- Messages