Hi,

Just discovered this project and I'm hanging around to see whether it can be used as a starter-kit for a full web platform on Laravel 5.1 with the following requirements:

• handling 15 000 companies with attached products
• multiple user account attached to one company
• email templates and email sending
• handling permissions at the user level: the idea is that the user will be able to buy different packages that will open some permissions / routes.
• elastic search integration for full-text search
• database query capacity for specific advanced query

that's about it :)

thanks for sharing your thoughts Cheers, Chris

I had a problem using October about user permissions. My intent was to enable ACLs based on his creator, like: root user creates admins, admins can create chief editors and chief editors can create editors. But in October backend everyone is a admin, so chief editors could add to themselves admin permissions.

Did you try blocking access to Manage other administrators?

thanks for your thoughts guys.

i read in the documentation that on top of the roles, you can add/remove permissions. Hence, even for an admin, it should be possible to remove the permission "manage-users" i guess ? (just theory)

anyone with the Elastic Search Integration experience here ?

Last updated 9 years ago

@daftspunk If "Manage other administrators" was blocked only the root user could create another users to the system, "chief editors" will not be able to create "editors".

@chris10207 That's my point, there is no "manage-users" options, only "Manage other administrators", every user on the system is a administrator you don't have roles, only permissions.

multiple user account attached to one company

Will be not so easy since there is no control in backend_users of who is the parent user, what user created this user. You will some effort to attach roles, parents and companies and get a rule like: The user A who is creating this user B, has C role and belongs to D company.

To make a long story, short: October isn't a multitenant system like a service in a cloud platform.

Last updated 9 years ago

Thanks Leo for the insights. i think i can go with only one level on User:

• attached to one company,
• with multiple permissions

for permissions related to user creation for one company, i think it is possible to filter by the company ID.

indeed more effort in term of development you are right

@leocavalcante Thanks for clarifying, I see what you mean now. We would need to improve the back-end permissions to allow for this complex user hierarchy.