Tabs and windows
Tab and window management
List, open, close, move, and organize tabs and windows without digging through menus.
Example prompts
- What tabs do I have open?
- Close the tab about…
- Open this URL in a new tab
Kahana · Oasis Enterprise
Enterprise browser buyer guide
Managed SaaS access, governance in the session, and how to evaluate Oasis next to your IdP and DLP programs
Why this guide exists
Most enterprise work now runs in the browser: SaaS, internal web apps, and increasingly AI-assisted workflows. Yet many security models still assume corporate laptops, VPNs, and network perimeters as the primary control points. When contractors and partners work from devices you do not own, that mismatch shows up as slow onboarding, policy gaps, or an expensive default to shipping hardware and standing up hosted desktops for roles that mostly live in a handful of web apps.
A managed enterprise browser is one answer to the gap: place governance where work actually happens, inside the browser session, and connect it to the identity and data-protection investments you already have. Oasis is built for that pattern: unified browser policy, IdP-backed sessions, and enterprise DLP alignment where your stack supports browser-level enforcement.
Below you will see the same session-governance visuals and capability blocks we use on the Oasis Enterprise Browser product page, plus evaluation topics for your team: benefits, deployment, UX, and FAQs framed with honest limits (what belongs in a browser vs what still needs other delivery models). For the personal AI browser experience, see Oasis Browser.
Oasis Enterprise in practice
Illustrative controls and capability layouts match the live product story: session-level visibility, device vs browser tradeoffs, and four enterprise outcomes with links to deeper feature pages.
Incident Control Center
27 incidents in the last 24 hours
Export CSVCreate automation
| Severity | Title | User | App | Status |
|---|---|---|---|---|
| Critical | Internal roadmap pasted into AI | Jordan Lee | Grok | New |
| Critical | Source code shared to ChatGPT | Alex Chen | ChatGPT | New |
| High | Customer PII pasted into Claude | Morgan Taylor | Claude | In progress |
| High | Unknown AI tool detected | Sam Rivera | Unknown AI | New |
| Medium | Financial data shared to assistant | Jordan Kim | Gemini | Resolved |
Go deeper on Oasis Enterprise
Prefer the full story? Oasis Enterprise Browser overview
When work moved to the browser, the control model had to follow
SaaS, internal web apps, and AI tools run in sessions that sit beyond classic device-only assumptions. Oasis treats that session as a first-class place for policy.
What breaks with a purely device-centric story
- Access is gated on shipping laptops, heavy imaging, or expanding hosted desktops for roles that mostly live in SaaS.
- Contractors and partners on unmanaged devices fall outside consistent browser enforcement.
- Sensitive activity in web apps is hard to govern if policy stops at the network edge or owned endpoint.
What browser-centric governance changes
- Enterprise rules apply inside the managed browser session where SaaS work happens.
- The same policy story can cover corporate and third-party devices when Oasis is in scope.
- Identity and data protection stacks can extend into workflows instead of stopping short of the tab.
What Oasis is built to deliver
Four capabilities map to how security and IT teams describe the job: external access, consistent governance, stack integration, and operational speed for web-first work.
Secure access for external collaborators
Partner and contractor work keeps landing in the browser, often on third-party devices you never issued. Oasis is a managed enterprise browser so unified browser policies and SaaS access expectations can meet people where sessions actually run—without treating hardware logistics as the only answer for every web-first role.
- Let external users work from their own devices when your program allows, with session-level expectations they can see and follow
- Shrink the set of cases where shipping machines or standing up hosted desktops is the default for browser-centric work
- How fast teams really go live still depends on your IdP, apps, and change management. Oasis removes one structural bottleneck, not every dependency
Step 1
Invite enterprise user
Step 2
IdP auth + MFA
Step 3
Managed session starts
Step 4
Sanctioned SaaS workspace access with policy
Consistent browser governance
Governance in the browser matters because if policy only follows a managed endpoint image, SaaS on unmanaged or partner-owned devices quietly drifts outside the same enforcement plane. Oasis applies unified browser governance so policies follow the session—what “good” means for extensions, data handling, and app access travels with it.
- Describe browser-level expectations once, then operationalize them instead of re-litigating them project by project
- Align extensions, sensitive flows, and app access to the risk tiers your security team already names in other forums
- Specific controls ship with the product roadmap and your configuration. This page states direction, not an exhaustive control matrix
Active profile: Enterprise browser baseline
Step 1
Session opened for sanctioned SaaS app
Step 2
Sensitive content detected in prompt field
Step 3
Download blocked by browser policy
Step 4
Event exported to SOC workflow
Connect to existing identity and DLP
Identity and DLP together answer who is in the session and what sensitive information is allowed to do. Oasis is designed so those investments extend into SaaS and web workflows instead of stopping where classic network boundaries used to.
- Tie browser sessions to your identity provider so access feels familiar to users and legible to auditors
- Carry enterprise DLP and data rules into the browsing environment where your stack supports browser integration
- Exact connectors, event shapes, and enforcement modes belong in architecture review with your IdP and DLP owners before procurement hard commits
Identity gate
- Okta SSO
- MFA verified
- Role: Enterprise user
Data policy
- Paste: inspect
- Download: restricted
- Upload: allowed
Decision engine: allow Sanctioned SaaS workspace session with DLP guardrails
Faster paths for external teams
When every new contractor waits on imaging or a fresh hosted desktop seat, calendar time stacks up, especially for roles that mostly live in a handful of SaaS apps. A managed enterprise browser with governed sessions can shorten time-to-productivity when your program allows identity-driven SaaS access instead of linear device logistics alone.
- Move more onboarding energy from “rack, ship, image” to identity, policy, and the handful of apps that matter for the role
- Support contractor-heavy programs with less linear ops overhead where browser access is the real bottleneck
- Not every workload belongs in a tab. Thick clients and regulated workflows may still need other delivery models; Oasis targets the web-first slice
IF app scope = Sanctioned SaaS workspace AND data class = Confidential
THEN enforce enterprise browser baseline + notify security
Last event: triggered 2m ago on enterprise user session
Who should read this guide
Buying-committee lenses for managed browser programs
This page is written for teams evaluating secure SaaS access on corporate and third-party devices. End-user productivity features for the personal browser live on Oasis Browser; the sections below map common questions by stakeholder.
Security leadership
Session governance, data handling, and AI usage in the browser; how policies follow external and contractor sessions; how Oasis complements IdP and DLP rather than replacing your stack.
IT and enterprise architecture
Delivery models, identity integration, logging, and where a managed browser reduces reliance on hardware logistics or hosted desktops for web-first roles (without promising every workload moves to a tab).
Program and business owners
Contractor onboarding speed, project kickoff friction, and operational cost of default laptop or VDI patterns when the real work is SaaS in the browser.
Enterprise
Value pillars
Themes that show up in security, IT, and program reviews
Third-party SaaS without default device sprawl
Give external collaborators a path to sanctioned apps with identity, session, and data expectations that match corporate-grade posture.
One control plane for browser policy
Apply browser-level policy from a single place for corporate and third-party contexts instead of hoping consumer defaults behave the same everywhere.
Operational leverage for security and IT
Reduce trade-offs between speed, cost, and control by meeting people where they work: the browser.
Value Proposition
Benefits of Oasis
Key advantages of choosing Oasis for your organization
A managed enterprise browser is one layer in a modern program: it can unify browser expectations for SaaS and web work, extend identity and DLP into sessions on third-party devices, and reduce how often hardware logistics or hosted desktops are the default answer for roles that are already web-first. It does not replace every legacy app or air-gapped workflow.
Security
Enhanced data protection and DLP (controls on copy/paste, download, printing, screenshots, watermarking).
Built‑in threat detection and prevention for phishing, malware, risky sites, and malicious downloads.
Identity-aware access to SaaS and internal web apps from the browser, which can reduce reliance on VPN and VDI for browser-centric roles when your architecture supports it.
Productivity
New ergonomic workflows that adapt to how you work, with spatial organization and intuitive controls that reduce cognitive load and improve focus.
Simplified IT operations by consolidating multiple security agents and web security products into the browser layer.
Potential to lower infrastructure and licensing pressure where browser-governed access replaces some VPN, VDI, or parallel web-gateway patterns. Scope depends on workloads and procurement.
Why the browser belongs in the security conversation
Third-party reporting continues to tie incidents to browser factors, phishing, and supply-chain paths. Use these as directional context in your own risk reviews, not as vendor-specific promises.
44%
Browser-related IR
Share of incidents where browser-related factors appear in industry incident research.
Source: Palo Alto Networks, 2024130%
Zero-hour phishing
Year-over-year increase in zero-hour phishing called out in browser security reporting.
Source: Menlo Security, 202515%
Third-party and partner paths
Of breaches involved a third party, including data custodians, third-party software issues, or other supply chain paths, in DBIR analysis.
Source: Verizon, 2024Single Sign-On
Seamless authentication with your existing identity providers
Key Points
- Integrates with common enterprise IdPs (for example Okta, Microsoft Entra ID, Ping)
- Built-in MFA support
- Seamless user experience
Implementation
Deployment experience
What to expect when deploying Oasis in your organization
Most teams pilot with a bounded user group, align IdP and DLP assumptions early, and expand policy coverage as confidence grows. Timelines depend on change management, app inventory, and regulatory context; plan proof points with your program office rather than assuming a fixed go-live window.
1
Integrate with your existing identity infrastructure
Oasis seamlessly connects with your current identity provider using industry-standard protocols including SAML, OAuth, and SCIM for user provisioning and authentication.
2
Distribute Oasis to your team
Deploy through your existing device management platform (VMware Workspace ONE, Citrix Endpoint Management, etc.) or provide a secure download link for self-service installation. The process is straightforward: download, install, and start using.
3
Users get up and running immediately
Team members authenticate through your existing identity system and can instantly import their bookmarks, saved passwords, and browser preferences for a familiar experience.
4
Gradually implement security policies
Begin with a pilot group and specific applications to develop policies that match your workflows. As you gain experience, expand to additional teams and use cases to build comprehensive security coverage.
AI, voice, and calm UX
User experience
The same client experience as Oasis Browser, including voice, assistant, confirmations, onboarding, import, and planned Amplifier feedback, ships in Oasis Enterprise Browser. What follows are the live product mocks from the consumer page; enterprise wraps them with policy, identity, and data controls.
Voice
Speak when it is faster, or go hands-free
Tap the microphone in the composer to open a focused voice session: a cinematic overlay with an aura visualization, capture modes (Continuous vs Precise), and whether replies are spoken or streamed into chat. Voice and typing share the same assistant thread.
Voice is available in supported builds and may require device permissions. Unavailable builds show a clear in-product message.
Status hints like "Listening" and "Pause briefly after you speak" mirror what you see in the product during capture.
Voice session
Listening
Pause briefly after you speak, or tap the orb to send now.
ContinuousPrecise|SpokenChat
Assistant
Actions grounded in your browser
The panel combines a chat timeline, a composer with "Ask Oasis…", read-aloud and feedback on the latest AI message, and readable busy states when a tool is running (for example, summarizing a page). Search and filter below to explore commands and skills: illustrative prompts, not an exhaustive list.
What can Oasis do?
Search in plain language to match ideas like "that article from Tuesday" or "clean up my tabs", then browse example prompts for each area.
Try asking
Filter by category
Tab groups
Tab groups
Create, rename, add or remove tabs, and list groups so a messy session stays scannable.
Example prompts
- List my tab groups
- Add this tab to the research group
- Rename my group to…
Bookmarks
Bookmarks and folders
Treat bookmark folders as first-class: list, create, rename, add tabs, open sets of saved pages.
Example prompts
- Show my bookmark folders
- Save this tab to…
- Open everything in my reading folder
History
Semantic search and history
Find pages by meaning—not only exact keywords—when you half-remember a visit.
Example prompts
- Find that article about…
- What did I read about… last week?
- Search my history for…
Page understanding
Summarization and page understanding
Turn long articles into short answers grounded in what you are viewing.
Example prompts
- Summarize this page
- What are the main points?
Saved context
Memory-style lookup
Search across what the assistant can access, including saved and visited context.
Example prompts
- Have I visited…?
- Find… in my saved stuff
Control
Confirmations for sensitive actions
When a command could change your browsing state in a meaningful way, Oasis can ask you to confirm. You see plain-language copy plus a highlighted command line so you know exactly what will run.
Illustrative modal below. Real copy and icons may vary slightly by version.
Confirm Action
This will close a tab and cannot be undone from the assistant. Continue?
Command: close tab "Quarterly report"
Onboarding
A short checklist to get to your first win
A docked checklist tracks basics like signing in, sending a first prompt, and trying voice, so you are not left wondering what to do after install.
Get started2 of 4
- Sign in to Oasis AI
- Try your first prompt
- Try voice conversation
- Explore tab tools
Switching
Import in seconds
Oasis uses a migration-style wizard so you are not rebuilding your digital life from scratch. One guided flow, clear choices, and OS permission prompts only when needed. Switching often takes seconds, not minutes.
- Bookmarks (or favorites, depending on source browser)
- Passwords
- History
- Form autofill data
- Payment methods (where supported)
- Extensions (where the platform can transfer them)
General
Import browser data
Bring your bookmarks, passwords, history, extensions, and autofill data from another browser.
Import data
Import browser data
- Chrome: kahana.co
- Chrome: Kahana
- Chrome: Adam
- Brave: Personal
- Safari
- Microsoft Edge: Profile 1
- Chromium: Work
- Passwords from CSV fileBookmarks from HTML file
Coming soon
Amplifier: learn from real feedback
Planned feature: tags, notes, and thumbs become the loop that steadies the assistant over time. Preview below.
Read the full Amplifier guide →
Most assistants miss the mark on real work: too slow, too wrong, or built for demos. Amplifier is our planned layer that learns from your tags, notes, and thumbs: session signal, not hype, so speed, accuracy, and quality can move the way you care about. Consistent feedback over 30, 60, and 90 days can compound; the chart is illustrative only, not a live metric or guarantee for your curves.
Your signal
Help us improve Oasis
Didn't workWrong resultToo slowSafety concernConfusingSuggestionOther
Add details (optional)…
Did we get it right?
Illustrative trajectory
Training correlates with better outcomes
Concept only: tags, thumbs, and notes feed a loop we plan to turn into steadier answers over time. Three dimensions rising here as feedback piles up. Not a guarantee, live dashboard, or your actual trajectory.
| Day | Speed | Accuracy | Quality |
|---|---|---|---|
| Day 1 | 28 | 22 | 24 |
| Day 30 | 52 | 48 | 50 |
| Day 60 | 74 | 76 | 78 |
| Day 90 | 90 | 92 | 94 |
Frequent Questions About Oasis
FAQs
Comprehensive answers to technical and business questions
Multi-View
Work with multiple applications simultaneously