Customer-specific attributes

just setup dolibarr for me and one other person to be able to collaborate on work for our customers. i have a feeling this is stuff which is probably already possible and i’m just struggling to figure out how. anyways if people want to point me in the right direction or if i’m misunderstanding what dolibarr can or is supposed to do, let me know. i’ll list a few things, thanks!

customer-specific attributes - i want to write down a username/password that a customer has, but not all my third-parties will have username/passwords that i need to store. also some might have 5 different ones.
a knowledgebase/wiki/articles - be able to put stuff into nested categories. whether for just me and the co-worker or if there can be separation of sections for me and the co-worker compared to customer’s which we provide services to.

If you don’t need the customer data (the usernames etc.) in a structured form, maybe it is sufficient to use the field for private notes, which is available for any third party?

Just one security remark, though: IT systems should never store an unencrypted password. In most cases it should not even store the password at all, just the hash of the password. I don`t know your intended use case, but this should be taken into consideration.

Regarding the wiki articles: Currently, there is an experimental module for knowledge management available (the value MAIN_FEATURES_LEVEL has to be set in the extended settings to make it visible). Since it’s experimental, it is not yet ready for production. But it’s good to know that development activities are happening around this topic.

thanks for the reply, it was just what popped in my head as an example so i wouldn’t have to waste effort trying to explain my actual attribute purpose and whatnot. agreed about security :+1:

will keep an eye on the knowledge management ty