Back to Top
m365-family-of-apps

How Access Works in Microsoft 365 at KAUST

Use this guide to understand access and review what you share. Microsoft changes its interfaces regularly, and the options available depend on the file, folder, link type, and organization settings. Check the permissions on the resource involved.

How these tools fit together

Microsoft 365 Groups connect many Teams workspaces and group-connected SharePoint resources. OneDrive sharing is managed separately, and not every SharePoint site or plan has the same membership model. Check the permissions on the resource involved.

Microsoft 365 Groups and connected resources

A Microsoft 365 Group maintains membership for its connected services, which can include a Team, a SharePoint team site, a group-connected plan, and a shared mailbox. Communication sites, channel sites, OneDrive items, and other plan types can have different access models.

Adding someone to a Group or Team can grant access to its connected resources. Check what they will be able to access before adding them. For a one-time meeting, invite them to the meeting without adding them to the Team.

Choose a tool, then choose a topic. You can also read all topics together.

OneDrive

Your personal cloud workspace

OneDrive is your personal work storage at KAUST. Think of it as your digital desk: what lives there is yours until you deliberately share it. Every KAUST account holder, regardless of whether they are staff, faculty, a researcher, or a student, gets OneDrive automatically the moment their account is created.

Key fact: OneDrive is provisioned automatically. You do not need to request it. You receive 50 GB by default, accessible at onedrive.com or through the Microsoft 365 portal at m365.cloud.microsoft.

Use OneDrive for

Draft documents still in progress. Personal notes and working files. Temporary collaboration with one or two colleagues. Files that belong to you as an individual.

Do not use OneDrive for

Department files that others need long-term. Research group shared content. Team documents that should survive your departure. Anything that genuinely belongs to a group, not a person.

If files only live in your OneDrive and you leave KAUST, your colleagues have a 60-day window to retrieve them before Microsoft permanently deletes them. Team content belongs in SharePoint.

Two ways to check what you have shared

Files shared weeks or months ago often quietly stay shared long after they need to be. Two tools help you keep on top of this.

The Shared by Me view

Use this view as a starting point for reviewing items you have shared. It is not a complete inventory of every way someone may have access.

1

Open OneDrive on the web.

2

Select Shared from the left navigation.

3

Select the Shared by Me tab.

If anything on that list surprises you, it is worth reviewing.

Manage Access (for a specific file or folder)

Review the item's sharing links and listed permissions. Check parent folders, sites, and relevant group membership too, because access can come from more than one place.

1

Locate the file or folder in OneDrive on the web.

2

Right-click it and select Manage Access, or select it and choose Manage Access from the toolbar.

3

Review both the Links section and the People section.

Choosing who can access and what they can do

When sharing from OneDrive, you make two decisions: who can access the file, and what they can do with it.

Who can access

Anyone

No sign-in. Forwardable. Use only for information authorized for public disclosure. Set an expiry matching when access should end where available; otherwise set a review or removal date.

People in KAUST

KAUST sign-in required. Use only when the intended KAUST audience is authorized to access the information. Internal classification alone does not authorize broad sharing.

Specific People

Named individuals only. Wrong person gets the link? It will not work for them.

Direct Access

An authenticated permission grant to intended recipients, rather than a sharing link. Direct permissions and Specific People links can both be appropriate; check other existing access too.

What they can do

PermissionWhat they can doNote
Can editOpen, change, save, deleteEdits affect the original file
Can reviewComment and suggest edits onlyWord, Excel, PowerPoint only. Not folders or PDFs.
Can viewRead only. Can still download.Add block download separately if needed
View, no downloadBrowser view only. No download, print, or sync.Screen captures are always possible

Use authenticated access limited to the intended recipients. Specific People links and direct permissions can both be appropriate; neither automatically removes other existing access. View access does not prevent every form of copying.

Setting an expiry date when sharing temporarily

KAUST does not currently impose a maximum lifetime for sharing links. Set an expiration date that matches when access should end, such as a project end, event end, or review deadline, where the feature is available. Otherwise, set a review or removal date.

When creating a new link

1

Select Share on the file or folder.

2

Open the available link settings before copying the link. The name and position of the control may vary.

3

If the link settings offer an expiration date, choose when access should end. If they do not, record a review or removal date.

4

Save settings and share the link.

Updating an existing link's expiry

1

Open Manage Access for the file or folder.

2

Under Links, find the link you want to update.

3

Open the link's available settings. If an expiration control is offered, update it. Otherwise, plan to review or remove the link when access should end.

4

Save any supported change. Check the resulting link settings and any other permissions that may still provide access.

Broad sharing without an end date needs a strong, continuing reason. Ending one link may leave other links, direct permissions, group membership, inherited access, or copies already obtained in place. Review those access routes too.

Information approved for indefinite public access should move to an approved public website. OneDrive and SharePoint should not be its permanent public publishing home. Specify the intended audience when requesting the site, obtain GBC approval before Internet publication, and publish only information authorized for that audience. Request a website (KAUST network or VPN required).

Removing access that is no longer needed

Good practice is to review your shared files periodically. The Shared by Me view takes less time to check than most people expect. Here is how to remove access when you find something that should not still be shared.

Remove a specific person

1

Open Manage Access for the file or folder.

2

Under People, find the person.

3

Select their permission level (Can Edit or Can View).

4

Choose Remove Access and confirm.

Removing one permission does not necessarily remove every access route. Check other links, direct permissions, group membership, and inherited access, then verify the result.

Delete a sharing link

1

Open Manage Access for the file or folder.

2

Under Links, find the link you want to remove.

3

Select the X next to it and confirm.

Deleting a link stops access through that link. Other permissions and previously obtained copies may remain. Anyone links cannot be revoked for just one recipient; remove the link if it should no longer work.

If an existing Edit link cannot change to View, create an appropriate View replacement, share it with the intended recipients, and remove the old Edit link. Review other access routes too.

What happens when someone leaves KAUST

When a KAUST account is removed from Active Directory, Microsoft preserves that person's OneDrive for 60 days. During that window, their manager or a designated delegate receives an automated notification and can access and move the files. After 60 days, the OneDrive and everything in it is permanently deleted.

Files stored only in a personal OneDrive are at risk. If important team or department files live in one person's OneDrive and that account is removed, the 60-day window is easy to miss. Team content belongs in SharePoint.

Before leaving KAUST

Move team or department files to the correct SharePoint site. Confirm with your manager which files need to remain accessible. Complete moves before your final working day.

For managers and team leads

When a team member moves on, review their Shared by Me view during the 60-day window. Copy required files into the appropriate SharePoint site. Make sure ongoing team content is not stranded in personal storage.

SharePoint

These site-permission instructions describe regular SharePoint sites. Manage private and shared channel membership through Teams, and check separately granted item access when needed.

Where teams store shared content

SharePoint is Microsoft 365's platform for content that belongs to a team, department, or project, and needs to remain accessible regardless of who comes and goes. All SharePoint sites at KAUST include 100 GB of storage by default.

Key fact: SharePoint sites at KAUST must be requested through KAUST IT. They are not self-service. This is a deliberate governance decision.

Team Site

A group-connected team site supports collaboration and stores team content. A Team has a connected SharePoint site. Group membership can grant access to related services, but check the actual plan, site, and item permissions.

Communication Site

Not connected to a Group. Designed for one-to-many publishing such as news, guidance, and policies. No associated Planner or Teams space. Permissions managed directly in SharePoint, not through group membership.

How to request a SharePoint site at KAUST

All new SharePoint sites must be requested through KAUST IT at it.kaust.edu.sa/about/contact-us. Before you contact IT, have the following information ready.

ItemWhat to provideExample
Site nameClear, durable nameGraduate Funding Portal
Preferred URLkaust.sharepoint.com/sites/Namekaust.sharepoint.com/sites/GradFunding
PurposeWhat the site is forShared workspace for funding documents
Site ownersAt least two KAUST email addressesname@kaust.edu.sa
Members and accessWho needs access and at what levelTeam A: Member; Team B: Visitor
External sharingAny external domains neededaramco.com or None

Every site should have at least two owners from the start. If one owner leaves or changes role, the other can continue to manage the site without it going unmanaged.

Groups, permission levels, and what they mean

Regular SharePoint sites commonly use Owners, Members, and Visitors groups. Private and shared channel sites have a different membership model managed through Teams. Check which type of site you are working with.

Owners

Full Control. Manage settings, people, libraries, and permissions. The site is their responsibility.

Keep this list small and intentional. Too many owners = no clear owner.

Members

Edit permissions. Upload, change, and delete content. Regular contributors.

Cannot manage site settings or other people's access.

Visitors

Read only. View files and pages without making any changes.

Right for audiences who need access to information but not to contribute.

Permission levels behind each group: Owners get Full Control (everything), Members get Edit (add/change/delete content), Visitors get Read (view only). Custom permission levels exist but for most sites the defaults are cleaner and easier to maintain.

Adding and removing members

How you add members depends on whether your site is connected to a Microsoft 365 Group (most team sites) or standalone (communication sites).

Group-connected team sites (recommended approach)

For a group-connected team site, manage membership through its Group or Team. This updates group-connected access. Review any separate site or file permissions and the plan involved.

1

Open the SharePoint site.

2

Select the Settings gear, then Site permissions.

3

Select Add members and enter their name or KAUST email.

4

Choose Owner or Member. For read-only Visitor access, add them directly to the Visitors group instead.

Adding as Visitor directly (not through the Group) gives SharePoint access only. They will not appear as a Team member and will not get Planner access. This is intentional for read-only audiences.

Communication sites

Not connected to a Group, so all access is managed directly through SharePoint groups. Add the person to the Owners, Members, or Visitors group as appropriate through Site permissions.

For a group-connected site, remove Group or Team membership when that access is no longer needed. For site-only permissions, use the site's available permission controls. Check separately granted or inherited access before treating removal as complete.

How permissions flow and what breaking inheritance means

By default, permissions flow from the top of a site down to everything below it. You set access in one place and it cascades everywhere.

Site
→
Libraries
→
Folders
→
Files

Change the site permissions and it cascades down through everything that inherits.

Key fact: Breaking inheritance on a library means it stops following the site's permissions and manages its own. Changes at the site level no longer affect it. You must manage it independently from that point.

Good reasons to break inheritance

One library has content that only a smaller group should see. A library should be read-only while the rest of the site is editable. Leadership, HR, or financial documents in a shared general site.

Avoid breaking inheritance on

Individual scattered files and folders. Items where a separate library would work better. Anything creating a permissions map nobody can maintain.

How to break inheritance on a library

1

Open the document library.

2

Open Settings, then go to Permissions for this document library.

3

Select Stop inheriting permissions and confirm.

The library now has its own independent permissions. Review and adjust access before anyone relies on it.

Libraries and when to use unique permissions

A document library is the primary container for files on a SharePoint site. Every site has at least one default library, usually called Documents. You can create additional libraries for different purposes.

Good uses for separate libraries

Financial or HR documents with tighter access. Published reference materials that should be read-only. A specific project with its own membership.

What each library can have

Its own permissions (break inheritance). Its own column structure and views. Its own versioning settings. A clearly named access group.

Best practice for sensitive content: Create a dedicated library, break inheritance on it, assign access to a clearly named group, and keep the number of permission exceptions low. Do not scatter sensitive files across a general library and try to protect individual items individually.

Restoring inheritance

To return a library to following the site-level permissions, open its Permissions page and select Delete unique permissions. This removes any custom permissions you set on that library and everything inside it will revert to the site defaults.

Checking who can access what

Where available, Check Permissions helps you inspect a person's access at the site or item you are checking. A result at one scope is not a complete inventory of access elsewhere.

1

Open Site permissions from the available site settings. You may need the advanced permission settings.

2

If available to you, select Check Permissions.

3

Enter the person's name or email address.

4

Review the permissions shown and their source. Check relevant group membership and any library, folder, or item with separate permissions.

Use the result with the relevant links, permissions, and membership checks. If the result is unclear or you need a site-wide review, contact IT Support.

Scenario where this is useful

A colleague says they cannot access a library you thought they had access to. Run Check Permissions on their account to see exactly what they have, and identify whether the gap is at the site level, the library level, or from a broken inheritance chain.

A sharing report is a starting point, not a complete permission inventory. Individuals can generate their own OneDrive sharing report. For a full SharePoint sharing report, contact IT Support and include the site's main SharePoint URL. Review links and membership alongside the report; absence from a report does not prove that no broad access exists.

External access at KAUST

By default, SharePoint sites at KAUST do not allow external access. The platform is configured for internal collaboration unless IT specifically enables external access for a site.

Do not attempt to share a SharePoint site externally without contacting IT first. External access must be enabled and scoped to specific approved domains before any external sharing works.

Collaborating with external partners

Contact KAUST IT and specify the domains you need access for, for example aramco.com or kfupm.edu.sa. IT will enable access scoped only to those domains. Not opened broadly.

Anyone access on SharePoint

Technically available but requires a strong academic or business justification. Subject to review by IT and Information Security. Approach with caution and only when genuinely necessary.

IT provides the platform and manages the sharing settings. Site owners are responsible for what is uploaded to their sites and how it is shared once external access is enabled.

Microsoft Teams

How Teams and Microsoft 365 Groups connect

A Team is a collaboration workspace for chat, meetings, files, and channels. But there is something important running underneath every Team that most people never see.

A Team uses its associated Microsoft 365 Group for membership. This grants access to group-connected resources. Private and shared channels have their own membership and SharePoint sites, and other permissions may apply to particular files.

What you get when you add someone to a Team

Teams channels
+
SharePoint site
+
Planner boards
+
Group mailbox

Adding someone to a Team for one meeting can give them unnecessary access to connected content. Review the intended audience and permissions, especially for sensitive information. Invite them to the meeting without adding them to the Team when full membership is not needed.

Requesting a new Team at KAUST

Teams at KAUST are not self-service. All new Teams must be requested through KAUST IT at it.kaust.edu.sa/about/contact-us. This is a deliberate governance decision to prevent unchecked sprawl and orphaned workspaces.

Information neededWhat to provide
Team nameA clear and purposeful name
PurposeWhat the Team will be used for
OwnersAt least two people always. If one leaves, the other keeps things running.
Initial membersWho should be added at launch
External accessWhether external collaborators are needed and who

Create a new Team when

The group has fundamentally different membership from any existing Team. The collaboration is long-term. The group genuinely needs its own separate space.

Create a new channel instead when

Same people, new topic or sub-project. The discussion fits within the scope of the existing Team. A new Team would create unnecessary sprawl.

Standard channels: the default and the right choice for most work

Standard channels are visible to every member of the Team. They are where most day-to-day collaboration should happen and where most files should live.

Key fact: Files uploaded to a standard channel are stored in the Team's connected SharePoint site, in the Documents library, in a folder named after the channel. A channel called Research Data stores files in a SharePoint folder called Research Data.

Visibility

All Team members can see all standard channels and their content.

File storage

Files go to the Team's main SharePoint site. Accessible directly in SharePoint by any Team member.

Limits

Up to 1,000 standard channels over the lifetime of a Team.

Apps supported

Planner, Forms, Stream, OneNote tabs, and many third-party apps.

For most Teams and most teams of people, standard channels are all that is needed. Private and shared channels introduce significant complexity and should be used only when there is a genuine reason for them.

Private channels: isolated by design

Private channels limit conversations and collaboration to their members. Team owners who are not channel members can see the channel in Manage team, but cannot read its content simply because they own the Team.

Critical: Every private channel gets its own completely separate SharePoint site collection. Not a folder in the Team's main SharePoint. A completely separate site. Being a Team owner does NOT give you access to a private channel's SharePoint site unless you are also a channel member.

How private channel storage actually works

Team's main SharePoint site

Standard channel files. Accessible to all Team members.

≠

Private channel SharePoint site

A separate channel site whose membership is managed through Teams. Team ownership alone does not grant access to its contents. Review any separately shared files or notebooks for additional access.

Good uses for private channels

Leadership or management discussions. Sensitive workstreams for a subset of the Team. Confidential coordination that should not be visible to the wider group.

Limitations to know

Guests cannot create private channels. Planner, Forms, and Stream tabs are not supported. A private channel cannot be converted to a standard channel. Channel limits can change; check the current options with IT Support.

Shared channels: working across organizations

Shared channels let you collaborate with people from outside KAUST without making them full guests in your KAUST tenant. Like private channels, every shared channel gets its own separate SharePoint site.

Key fact: External participants in a shared channel appear with their own organisation's accounts, not guest accounts in KAUST's tenant. They only see the shared channel. Nothing else in the Team or the KAUST environment is visible to them.

FeatureGuest access (standard channel)Shared channel
How they appearGuest account in KAUST tenantOwn organisation's account
VisibilitySees all standard channels they are inOnly sees the shared channel
File storageTeam's main SharePoint siteShared channel's own separate SharePoint site
PermissionsManaged in TeamsCannot be managed independently in SharePoint. Teams controls it.

For an ongoing, structured collaboration with an external organisation, shared channels are generally cleaner than guest access. For a one-time meeting with external people, send a meeting link. They can join without being added to the Team at all.

Where files live and the difference between chats and channels

One of the most important things to understand in Teams, and one of the most frequently misunderstood: where your files actually go depends entirely on where you share them.

Where you shareFile stored inWho can access
Standard channelTeam SharePoint siteAll Team members
Private channelPrivate channel's own SharePoint siteChannel members only
Shared channelShared channel's own SharePoint siteChannel members only
1:1 or group chatSender's OneDrive for BusinessChat participants only
Channel meeting recordingChannel's SharePoint siteAll channel members
Personal meeting recordingOrganiser's OneDriveOrganiser manages sharing

Files shared in a 1:1 or group chat live in the sender's OneDrive. If that person leaves KAUST, those files enter the 60-day deletion window. For files the team needs to keep, upload them to a channel instead of sharing them in a chat.

Managing membership and understanding owner vs member roles

For a Team and its group-connected resources, manage the Team membership consistently. Check channel membership and any separately granted resource permissions too.

Manage Team membership through Teams. Adding someone directly to a regular SharePoint site can give them site-only access without adding them to the Team or its other group-connected services. Channel site membership is managed through Teams.

Adding a member

1

Open the Team.

2

Select the three dots next to the Team name.

3

Select Manage team or Add member.

4

Enter the person's name or KAUST email, then choose Member or Owner.

Removing a member

1

Open the Team and select Manage team.

2

Find the person and select Remove.

Removing someone from a Team also removes them from that Team's private channels. Review separately granted file or site permissions to identify any other access that remains.

RoleWhat they can do
OwnerAdd and remove members, create and delete channels, manage Team settings, delete the Team. Every Team must have at least two owners at all times.
MemberPost in channels, upload files, attend meetings. Can create private channels if the owner permits.

External access: guests, external participants, and cross-org collaboration

Teams supports several models for working with people outside KAUST. Choosing the right one matters both for usability and for keeping data appropriately contained.

Adding external guests to a KAUST Team

A guest is a named individual from outside KAUST invited into the Team. They get access to standard channels and, as a consequence of being in the Team, access to the connected SharePoint site. Review what is in the SharePoint site before adding guests. Restricted content should be in a library with separate permissions before any guest arrives. Guests cannot create private channels.

KAUST people in an external Team

When a KAUST person is invited as a guest into a Team hosted by another organisation, they use their KAUST credentials. They can only access the channels they are invited to. Files they access live in that organisation's SharePoint, not in KAUST's environment. Files they share from their KAUST OneDrive remain in their KAUST OneDrive.

Shared channels across organizations

External participants in a shared channel use their own organisation's accounts. They only see the shared channel. No visibility into the rest of the Team or KAUST's environment. Permissions cannot be managed independently in SharePoint: Teams controls access entirely. Removing someone from the shared channel removes their access to the channel's SharePoint site.

For a one-time meeting with external attendees: Send a Teams meeting link. They join as external participants without being added to the Team. No SharePoint access implications at all.

Dos and Don'ts

Things that work well

Use channels for anything the whole team might need to find later. Channel content is searchable and persistent.

Make sure at least one Team owner is a member of each private channel to maintain governance visibility.

Keep at least two owners on every Team and review membership when people change roles.

For one-time meetings with external people, send a meeting link rather than adding them to the Team.

Things to avoid

Adding someone to a Team just so they can attend one meeting. Send a meeting link instead.

Storing important files only in chat. Files in 1:1 and group chats go to the sender's OneDrive and are at risk if that person leaves.

Creating a new Team for every project. Ask whether a channel inside an existing Team would work just as well.

Assuming auditing a Team's content means checking only the main SharePoint site. Private and shared channels each have their own separate sites.

Microsoft Planner

Your visual task management tool

Microsoft Planner is a visual task management tool that lets you create tasks, assign them to people, set due dates, and track progress using a drag-and-drop board. It is built for lightweight project and task coordination.

Key fact: Planner Basic is available to every KAUST account holder through Microsoft 365. No request and no additional license is needed. Access it at planner.cloud.microsoft or directly inside Teams by adding a Planner tab to a channel.

What you can do with Planner Basic

Create and assign tasks, set due dates, drag-and-drop board view, file attachments, comments, and integration with Teams, Outlook, and Microsoft To Do.

When Planner fits well

Team to-do lists, simple group project tracking, personal work organization, task coordination alongside a Teams channel.

How Planner connects to SharePoint, Teams, and Groups

This section describes KAUST's group-based Planner request process. Membership and sharing can differ by plan type. Check the plan and its connected resources before assuming their audiences are the same.

At KAUST, standalone Planner boards are not permitted. All Planner boards must live within an existing Group. You cannot create a Planner board without a Group behind it.

The cross-grant access chain

Add someone to Group
→
Teams access
+
SharePoint access
+
Planner access

Adding someone to a Team also gives them Planner access. Adding them to Planner also gives them SharePoint access. The three tools share one membership layer.

Files attached to Planner tasks

Files attached to Planner tasks are stored in the linked Group's SharePoint document library, in a folder called Planner. Accessing them in SharePoint requires the same level of access as the rest of the site.

Being added directly to a SharePoint site without being in the underlying Group does not automatically grant Planner access. Planner access comes from Group membership. This is a common source of confusion when people can see a SharePoint site but cannot access the Planner board linked to it.

Planner Basic vs Planner Premium at KAUST

FeatureBasicPremium
Task creation and assignmentYesYes
Board viewYesYes
Teams and Outlook integrationYesYes
Timeline (Gantt) viewNoYes
Task dependenciesNoYes
Custom fields and labelsNoYes
Visual progress dashboardsNoYes
License requiredIncludedProject Plan 5

To request Planner Premium: go to m365requests.kaust.edu.sa and request the Planner and Project Plan 5 license. Include a short explanation of how it will support your work. The request routes to your line manager for approval.

Requesting a Planner plan at KAUST

Because all Planner boards must live within an existing Group, you have two routes depending on your situation.

Route 1: A Team or SharePoint site already exists

Ask the Team owner to add a Planner tab to a channel. This creates a Planner board inside the existing Group. No IT request is needed.

1

Open the Team and go to the relevant channel.

2

Select the + (Add a tab) in the channel tabs.

3

Search for Tasks by Planner and To Do and add it.

4

Choose to create a new plan or attach an existing one.

Route 2: No existing Group yet

Visit Contact Us to request IT support for setting up the Group and Planner board together.

Include in your request:

Name and purpose of the board

Who should be the owner

Who should be members

Good Practices

Good data governance across OneDrive, SharePoint, Teams, and Planner comes down to consistent habits applied at the right moments.

When someone joins your team

For a Teams workspace, add members through Teams. This updates its connected Group membership. For read-only access to a regular SharePoint site without full Team membership, the site's Visitors group can be appropriate. Check permissions on each resource involved.

When someone changes role or moves to a new team

Review access from the previous role and remove or adjust what no longer fits. Removing someone from a Team also removes them from its private channels. Check separately granted site or file permissions for other access that remains.

When a project ends

Take five minutes to review the Team and SharePoint site membership. Remove anyone involved on a temporary basis. Check whether the Team is still actively needed or should be archived. Teams that sit unused with active membership and open permissions are a governance risk.

When adding external collaborators

Before adding a guest to a Team, review what is in the connected SharePoint site. Restricted content needs to be in a library with separate permissions before the guest arrives. For one-time meetings, send a meeting link rather than adding the person to the Team.

When deciding where to store files

Ask whether the file belongs to you as an individual or to the team. Personal drafts go in OneDrive. Team-owned, long-term content goes in SharePoint or a Teams channel. Files shared in a chat stay in the sender's OneDrive and are at risk if that person leaves.

When reviewing permissions

Use Check Permissions where available and the Shared by Me view as starting points. Review the relevant links, site and item permissions, and group membership too. Reports and views are not complete access inventories, and a missing entry does not prove that no broad access exists.

When content is sensitive or Restricted

Keep Restricted content out of general document libraries. Create a dedicated library, break inheritance so it has its own separate permissions, and assign access only to the people who genuinely need it. Do not scatter sensitive files across a general library and try to protect them individually. If external sharing of Restricted content is ever needed, consult IT first.

The general principle

Use the most restrictive option that still lets the work get done. If Specific People works, use it instead of People in KAUST. If a channel post works, use it instead of a chat. If read-only works, use it instead of edit. Access should reflect genuine need, not convenience at the point of granting it.

Get help with access

Check the Data Classification Policy and Data Classification Procedure on the KAUST Policy site (KAUST network or VPN required). For classification and audience guidance, read Data Responsibility at KAUST.

Contact IT Support