On 18 Nov 2018, at 18:31, 'Blaxton' via Kotti wrote:
following kotti user manual document:
1- created 3 users.
2- created 3 groups and added each user to respected group:
Joe to prospects group, Sally to existing_clients group, and Xavier for the legal_affairs group.
3- created 3 top level section:
Prospects section, ExistingClients section, and Legal Affairs section
4- shared each section with respected group:
shared Prospects section with prospects group, ....
5- tried to login with joe user id, but couldn't.
loging pages goes to try with no time out.
6- had to share "kotti home page" with "prospects group" to give view permission to be able to login as joe
but then joe can see all other sections.
apparently we have to share "Kotti Home Page" with user or group to be able to loginand that gives a global view to group.
What I want is:
members of prospect group, like joe, only able to view prospect section
and not other sections.
is it doable ? if yes , how ?
Everything is doable. Literally. In fact Kotti's workflow system is as flexible as it gets and probably one of its best features.
Did you find https://kotti.readthedocs.io/en/latest/developing/basic/security.html yet?
What you might want to do to achieve the above is to publish "Kotti Home Page" (transition it from state
public). With the default workflow it will then be "visible" to all users (even unauthenticated) and doesn't need to be shared. The (default) role to permission(s) mapping for each state can be found in
You can completely customize all of this in your own
workflow.zcml and make Kotti use that (instead of its default) by specifying
kotti.use_workflow in your
On 21 Nov 2018, at 22:39, 'Blaxton' via Kotti wrote:
1- Enabling user self registration document !!!!Do I need to install an add on to enable user self registration ?or self registration comes with default Kotti installation.
You can set
True in your
.ini file to enable user self registration. You can also set
kotti.register.role to automatically assign group(s) or global role(s) to users upon their registration.
2- Adding a new table to have user address, user billing, or other user profiles items,
that points back to principals table with foreign key.
You could subclass
kotti.security.Principal to add the desired attributes. Make sure to also add
id = Column(ForeignKey(Principal.id), primary_key=True) for the foreign key. Then also subclass
kotti.security.Principals and override the
factory class attribute to point to your
Principal subclass. The last step needed would be to set
kotti.principals_factory (also in your
.ini file) to point to your
such table should be filledwhen at the time of user registration.
You'd still need to implement the views/forms to allow editing of your attributes yourself though.
Having a document or an add-on to add user profile for billing purpose real helpsin project startup.
You're welcome to add a section on that topic to the docs! ;-)
To post to this group, send email to ko...@googlegroups.com.
Visit this group at https://groups.google.com/group/kotti.
To view this discussion on the web visit https://groups.google.com/d/msgid/kotti/1E9BADEF-B31C-4F40-841A-C275F89CEDBD%40binary-punks.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Kotti" group.