Spec:

• Create django users
• Groups
• Permissions

Users

Should use default Django User object (django.contrib.auth.models.User)
Users have extra field: key, this should be a unique generated token that can be used to contact the api. This way users can be added to an entity and update/delete/add records/zones without having to specify the atomiadns email/password.

Groups

Use the Django Group object, add 2 fields (username/password) for accessing the atomiadns services. Groups are the entities that have access (companies fex)

Permissions

Users can be assigned permissions that can specify what exactly they can do. However this is only on object type level, we will not implement accesslevels lower than fex: "can update records", "can delete records", "can view records", "can update zones", "can add zones",...
If we would want to do permissions on record level or zone level we would have to keep local information about zones/records. At this time I don't think that would be a good idea.

I've made this issue so people can comment and add extra information/questions.

from the zonedit page https://dns.sejo-it.be/edit/domain.ext
does work with chrome

the (+) icon just doesn't do anything :(

why session can't expires for closed Browser
i try login a account done. next closed Browser and open Browser again my account auto login