Possibility to have a read-only user(account)
Be able to grant just read-only permissions to users(accounts) so others (aka the chickens) can look at project progress etc. without the risk of messing up things. In our (larger) company it's almost impossible to set up all kind of webpages and use velocity which would probably work as well...
Statement from Kunagi Team
Read-only user accounts is a feature that we find to difficult to implement compared to the niche value added. Instead, see sto249, which will allow exported websites to be served by Kunagi directly. This should reduce the overhead for exporting read-only information.
Status
Issue is closed.
Comments
Thu, Nov 14, 2013, 14:47 by Witek (SM,T)
Would it be sufficent, if Kunagi itself would host the generated homepage? That way, no extra webserver would be required. And the Kunagi admin wouldn't have to manage so many users.
Sat, Nov 23, 2013, 21:33 by Martin
On itself it that would probably solve half the issue, as such a webpage should be available for each project in every Kunagi instance running. If such a page could be initiated when a new project is set up that would be great.
On the other hand one 'standard' account with RO permissions (available per project) would also do the trick. Also that way Kunagi admins don't need to manage extra users.