Permissions are inherited.
Access is inherited from the connected source. Adding knowledge to June never makes it visible to everyone.
Knowledge Base 
June12 documents
Your knowledge. June answers.
Bring your handbooks, policies, and how-tos into June. Put it to work with answers that respect each employee’s source permissions and link back to the original guidance.
app.juneops.com/knowledge
JuneAgent
Requests
Reachouts
Signals8
Access
Policies
Intelligence
Runbooks
Knowledge Base
Resources
Assets
Software
AI usage
Employees
Groups
Departments
Locations
Knowledge Base
All sources
Company knowledge, connected.
| Document | Status | Citations |
|---|---|---|
Connect to the company VPN IT handbook | In inventory | 24 |
| Set up your new laptopIT handbook | In inventory | 18 |
| Move your authenticator to a new phoneIT handbook | In inventory | 16 |
Your first day, step by step Employee guides | In inventory | 12 |
| Set up your home workspaceEmployee guides | In inventory | 10 |
| Book a room and start a meetingEmployee guides | In inventory | 9 |
| Request software for your teamSecurity & access | In inventory | 7 |
| Store and share passwords safelySecurity & access | In inventory | 6 |
| What to do if a device goes missingSecurity & access | In inventory | 5 |
Showing 9 of 12 documentsRefreshed Sep 18 · 9:00 AM
Start with the knowledge your team already has.
ConfluenceGoogle DriveGood answers start at the source
A little context goes a long way.
Choose what June knows. See what’s connected. Follow your guidance into the conversations where it helps.
Knowledge BaseAdd source
START WITH WHAT MATTERSYour content.
Your content.
Your choice.
Choose the spaces, pages, or folders June should draw from. Keep your guides where your team already maintains them.
Selected folders include their current and future content on the next sync.
Source nameIT handbook
IT handbook3 documents
3 documents selectedReady to review
Company knowledge, with boundaries intact
Nobody sees an answer they shouldn’t.
June inherits permissions from Confluence and Google Drive. Answers reference only sources the employee already has access to.
Shared guides stay shared with the right people. June brings the guidance into the conversation, with a link to the original.
Explore the source
ThreadDirect message · June
How do I connect to the company VPN?
1 reply
Here’s how to get connected:
- Open the company VPN app on your work laptop.
- Sign in with your work account and approve the sign-in prompt.
- Select Connect. You’re ready to go.
If you’re still having trouble, reply here and I’ll help.
Source permissions checked for Jordan.Access inherited
Shared, not broadcast.
Team guides and shared documents are referenced only for employees who have access to them.
See what gets used.
Follow citations into real conversations and review the feedback. Find the guidance your team comes back to.
Frequently asked
Where does June’s knowledge come from?
Connect company content from Confluence and Google Drive. Choose the spaces, pages, or folders you want June to use, and organize them into named sources.
Does June respect existing document permissions?
Yes. June inherits access permissions from the connected source. Answers reference only sources the employee is allowed to access in Confluence or Google Drive. Shared content follows those same permissions; adding a source to June does not make it available to everyone.
Can I choose which content to include?
Yes. Select the content for each source before adding it. For selected folders, current and future descendants are included on the next sync.
Can employees see where an answer came from?
June can include links to the documents used in an answer, so employees can read the original guidance and see the context behind it.
How do I know a source is up to date?
The Knowledge Base shows source sync status and document refresh information. Keep maintaining the original content in your connected workspace, and check its sync status in June.
Can I see how the knowledge is being used?
Each document has a citation history. See the conversations it appeared in, who asked, when it was cited, and resolution feedback where available.