Feature Request

Reviewers are not showing as on option to select under Article information > Contributors > Manage. If they are reviewing articles and commenting on them prior to publication, they should be listed as contributors in the Article information section.

Currently, to convert an SSO account to a standard account, we need to delete the user and re-add them. It would be highly beneficial if we could directly convert SSO accounts to standard accounts.

I have a lot of Team Accounts and Readers within my project and I prefer that they access the documentation exclusively through SSO. However, in the event of an outage, they should also have the ability to log in via the general Document360 login. In such cases, I would need to either add another account as a standard user or enable self-registration. In this scenario, I expect my team members and readers to be consolidated under a single account. However, Document360 currently treats them as separate accounts, which impacts various areas, including analytics and granular access management. Therefore, we request that both standard login users and SSO users be mapped under the same account, treating them as a unified entity. The same approach should apply to readers. Implementing this change would avoid confusion and significantly reduce the manual work from an administrator's perspective.

Document360 allows the various content roles to be created, however the flexibility to combine privileges to match specific user scenarios as customer might need is missing. For an example, it is not possible to grant only “View” and “Delete” privileges, or only “View” and “Publish”. When we reate a role with “Publish” privileges automatically “Update” and “Delete” get added as well. This is very limiting, since we have roles that should be able to publish but not delete. This flexibility, allows us to set clear structure in setting up a team for editing.

Currently, the system allows users to choose options under Create Team Account >> Content Access >> All, Workspace, Languages, and Categories, regardless of the pricing plan. For the Free plan, the Users & Security >> Content Access feature is not applicable. However, the dependency on this module still exists when creating a team account as described above. This functionality should be restricted for the Free plan. Content access >> None or All option will be applicable while creating the new team account & the other options will be grey out and tooltip message to be conveyed that "Please upgrade to professional plan"

The word "everything" is not informative. The "Owner" description should say something like "...access to general settings, team auditing, backup and restore, notifications, billing, and API". Also, "Admin" should logically come between Owner and Contributor.

I wish i had the ability to set the password policy (characters, expiration etc) for all of my users. I also wish i could incorporate custom fields - so they can tell me more about them (their company, their address, phone number, title etc). Right now, i can only search by email domain or name - harder to sort thru.

One of the customers has raised a request to include the login history for the team accounts and the readers in the KB portal. Please check this request and share your thoughts.

From what I understand, if a user is removed from Document360, all of their activities recorded under their ID will be changed from their name to “anonymous”. Therefore, if a user published articles or wrote comments in a chat discussion for example, their name will no longer be listed in those respective areas, and the article history will not accurately capture who did what in an article. As you know, we keep all of our Company’s policies and procedures on Document360, so it is critical that we keep an accurate and static log of all article activities regardless of whether a user has been removed from Document360 or not. Turnover is apparent in every company, so we need to ensure what was done by a user previously is not lost, especially considering the criticality of what we have stored on Doucment360. Please advise on the above as we need an immediate solution. Tradexport.com

I would like to be able to map contributor emails, so that if a contributor must be deleted and added with a new email, the article contributor is not lost in the transition.