Managing users, groups, and access
Hint: One Topincs user account can be shared by several people, because multiple sessions with the same user account are possible.
Topincs allows multiple users to access and edit the data stored.
Getting an overview of user accounts
From the start page you can reach the admin section. There you find a link to the page giving you an overview of the user accounts.
Creating an user account on the command line
How to create an user account
This way of creating users always works and requires an administrator to perform the creation of the user account on the command line.
Online registration
Store configuration
Hint: Make sure at least one user account is in the group Adminstrator and has an email address!
Topincs online registration can be controlled with two store
configuration parameters. By setting
registration.active you can decide whether you want
users to be able to register via the start page. You can adjust
whether an administrator has to look at registrations before
they are processed further with
registration.public. In any case you need to make
sure that mails can be sent from your server. If you deactivate
public registration, an administrator needs to be informed that
there is pending registrations. He will be notified by
email. For this purpose, at least one user account needs to be
in the group Administrator and have an email
address. If an administrator accepts a registration, an email
with an activation link is sent to the user. If he rejects, the
user is notified. With registration public the user immediately
receives the activation email after submitting his registration
without administrator attention.
Access control
Hint: For sophisticated access rules based on domain logic use topic access filters.
Access to resources of a Topincs store can be controlled for
groups. With the shell script create-access-conf
you can create a store specific access configuration file in the
conf directory. This needs be adjusted to your
requirements. Detailed information on how to proceed in this
matter is available in access configuration file itself. The
implicit access configuration which is active with or without an
access configuration file cannot be overridden, e.g. an
unauthenticated user cannot edit.
