Per Project or Organization knowledge base

Have you considered using Notes rather than Knowledgebase for this? Then you could assign to a particular project.

Not quite sure offhand whether the current permissions would allow it. Perhaps if you did it per organization.

No, that means notes attached to the organization. If you look in the create note form, you need to select an organization, then have the option to allocate it also to a project and/or task.

Putting 'needs more info' til you have a chance to try it out.

Do feedback to say whether it works as you want.

Please reopen if this is still an issue.

Hello, I think this could be an issue. Basicly I have the same problems as ñull. In my case:

- I'm using notes for 'short notes' to my clients", like "hi, just finished the website today!"

- I don't use the Knowledge Base because
- it's not per project configurable
- I don't like the fact that I cannot add a new attribute from the add/know.. pages (I first have to create one for every new topic).

Now I created my own solution: use cck to add a custom integer field to the 'note' type containing two possible values: 1|Message 2|Knowledge.
Then I make a block with a filter on the new field to only display messages for example.

A better solution would be to have the knowledge-base contenttype to work just like the core book module. And of course one needs the ability to add the type to an organization/project.

Greetings Bas

Hi @Wappie08, I would suggest you look at the stormnotes module. If you want to follow this up further, please reopen this issue as then it will appear in the issue tracker again.

Reopening the issue and changing the status to feature request.

Yes make the knowledge base more granular make sense.
The view of user organization, option should be included to admin/user/permissions => stormknowledgebase module.
Storm architecture is multi organization. An authenticated user shouldn't have cross system access to anywhere without being part of enterprise, project or organization.
Yes it can be done by stormnotes but users will semantically end up in stormknowledgebase module coz it simply make sens.

@ronline,

The point of the Storm Knowledge base is that it goes across projects. Notes can be project specific.

Are you saying that users will end up at kb simply due to the name? If that is so, then do not allow your users access to the kb.

I think this issue has been answered - so re-closing.