Overview of Content-Level Permissions
Content-level permissions in ScreenSteps allow administrators to control access to specific manuals, chapters, or articles within a knowledge base. This means you can decide which users can view or edit particular pieces of content, rather than granting access to the entire site or knowledge base.
- Content-level permissions provide granular control over who can see or modify specific content.
- They help protect sensitive or restricted information within a broader knowledge base.
Key Terms
Content-level permissions: Settings that determine whether a user can view or edit individual manuals, chapters, or articles.
Manuals, chapters, articles: The main organizational units within ScreenSteps where information is stored.
View permissions: Allow users to see content.
Edit permissions: Allow users to modify content.
Background and Context
By default, when you grant a user view or edit permissions in ScreenSteps, they can access all content within the scope you specify. However, there may be situations where you want to make exceptions and restrict access to certain manuals, chapters, or articles. Content-level permissions enable you to do this by allowing you to exclude specific content from a user's access, even if they have broader permissions elsewhere.
Why Content-Level Permissions Matter
These permissions are especially helpful when you want most users to have broad access to your knowledge base, but need to restrict a few specific items. For example, you might want a team to view almost everything, except for certain internal policies or confidential procedures. In such cases, content-level permissions provide a simple way to manage these exceptions.
- They help maintain security and privacy within your documentation.
- They support compliance with organizational or regulatory requirements.
- They allow you to tailor access to the needs of different users or groups.