Controlling access to pages?

[nsw2206]

http://doc.wakanda.org/Data-Security...725889.en.html

If you give access rights for a data entry page to the "Operators" group, for example, this means that all users can use this page.

Where do we do this?

[Greg]

Actually, permissions currently are model based, meaning anyone can access the html page, it's the data you can restrict. You can determine permissions at many levels (class, attribute, even the model as a whole)... you assign groups to different aspects.

So the short answer: it's all in the model.

There has been talk of a mechanism to assign permissions to a physical html page for view, but nothing currently.

[nsw2206]

Thanks Greg, does the documentation need adjusting? Perhaps its a hint of whats coming... :)

[Greg]

I think the wording could use some tweaking. If it was confusing for you, it is for others as well. I don't think it's incorrect necessarily, but "page" is a loaded word in the context of the paragraph. I think something like datastore class fits better than page even though the intent of the section is to explain users and groups.

I am sure this thread is being watched, the documentation team is always on top of these threads.

[Arnaud Schmitt]

Hello,
Yes, sorry for this confusing description -- thanks Greg for clarifying this. This paragraph anticipates on planned but not existing features and is therefore not correct. Currently, permissions for accessing data are model based only and are not related to interface pages. I edited the paragraph so that the concepts remain valid but do not refer to "pages".
Best regards,
Arnaud

[nsw2206]

Hi Arnaud,
how long till page security exists? WAK2, WAK3??? thanks.

[Arnaud Schmitt]

Hello,
Sorry, we don't have a specific schedule for this feature.
Arnaud