Right now i cant find head´s and talis in how to set up so the user altså can edit the data.
In your scenario you do not need to use ACL, so set all fields to public and works only with conditions. If you want a field only in registration you can set it only to see on registration form. ACL are helpful for advanced use.
For example (
see also screenshot):
You have field group called "Egne oplysninger " with Availability set to Guest, so all registered users not have available all fields in this group. This is bad because you lost data of these fields.
The best way is to set ACL to public and show the fields only on registration.
Another problem of your configuration:
- you have "Forfatterprofil" fielgroup with ACL set to "forfatter reg"
- you have "Forlagspræsentation" fielgroup with ACL set to "forlag reg"
But these fields are already hidden by conditions, so you need to set to public.
Otherwise you have this:
- Guest make a registration as forfatter (this is ok)
- Condition Remove foreleg fields from form (this is ok)
- Guest Become Registered (this is ok)
- ACL remove forfatter fields (
THIS IS BAD, user is not guest and is not forfatter)
- Condition add to usergroup "forfatter"
Conclusion:
for your scenario set all Availability to Public, show/hide fields is already managed with condition.
Las bu not leat, i read someware here in the forum that the system have possibilty til redirect users at login depend af usergroup, but i can find the place to set it up
No sorry, in Easy Profile you can set redirect after login, but this works for all users
