Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark default "Author" for entities for users who are part of an organization #9927

Open
lightw1s3 opened this issue Feb 11, 2025 · 0 comments
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team

Comments

@lightw1s3
Copy link

Use case

A functionality is proposed whereby when a user creates content on the platform, if the user belongs to an organisation, the Author field will automatically be set to that organisation and no other organisation can be selected.

This is especially useful in the Enterprise version when you have to manage knowledge entered from several organisations so that none of them can publish information ‘on behalf of another’.

Current Workaround

Currently, the only way to do this is to enter all users in an organisation into a group and associate a new marking to both the group and the organisation so that this knowledge is only visible to them. However, this is a problem because when you manage multiple organisations it means managing multiple markings both at the group level in headquarters and from the main organisation, which could lead to security problems in terms of information handling.

Proposed Solution

An attribute could be managed from Security > Organisations as a switch where ‘Default Author’ could be activated. If this were active, users found in that organisation, at the time of entering knowledge, would not be able to modify the Author attribute.

If the feature request is approved, would you be willing to submit a PR?

No.

@lightw1s3 lightw1s3 added feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team labels Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
Projects
None yet
Development

No branches or pull requests

1 participant