SharePoint, without opening SharePoint.
Find it across the sites, and keep the list current from chat.
“@Ray find the vendor agreement on the ops site.”
What Ray can and cannot do in SharePoint
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
Runs on its own
What Ray reads in SharePoint
- Sites, drives, document libraries, and what changed
- SharePoint lists, their items, columns, and versions
- Site pages, attachments, and search across all of it
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Create a folder
- Rename a file or a folder
- Add a list item, or update one
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Delete a file, a folder, or a list item
- Create or delete a list, a content type, or a site
- Create a sharing link
How Ray works with SharePoint
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect SharePoint
One click, right where you asked. Ray posts a connect card, you authorise SharePoint with your own account, and the work you asked for picks up where it left off.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in SharePoint, and tell Dana it is being looked at.
Rename a SharePoint folder
- Waiting on
- your approval
What does connecting SharePoint to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect SharePoint and it can do the SharePoint part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Every person on the team connects their own SharePoint account, so Ray can only reach what that person can already reach, and the history in SharePoint shows who actually asked.
Security and permissions
- You authorise SharePoint on its own login screen. Your password never passes through Ray.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- Disconnect SharePoint in a message, or uninstall Ray and every connection it held is revoked.
More storage & files integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in SharePoint.
Free to start, no credit card, and it asks before it acts.