What’s new in August: faster, safer identity management

This month we focused on cutting down clicks, tightening least-privilege, and removing guesswork for IT & Security leaders at mid-sized businesses. You’ll see easier requests, cleaner imports, and clearer status across the product. Identity management should feel simpler—and safer.

TL;DR

• ⏱️ Scheduled access with start time, duration, reminders—now also in Slack—to reduce standing privileges.
• 🤖 AI imports: paste app lists or upload screenshots to generate clean CSVs in minutes.
• 🧭 HRIS improvements: bulk create/remove/unmap, better previews, and auto-refresh after sync.
• ✅ Approvals & audits: Approval Groups, sortable Access Requests, and precise responder tracking.
• 🔗 Integrations & reliability: smoother OAuth, API key auth, stronger pagination, service-account labeling, and branded login fixes.

Time-based access — least-privilege on a schedule

You can now request access for a specific window with a start date, start time, and duration. Approvers are notified at once, with a follow-up reminder if a request is still pending near the scheduled start. When the final approval lands, requesters get a clear confirmation, and task assignees are notified if any step is manual.

Already have access but need a higher role? Request temporary elevation, then we’ll automatically revert you to the original role at the end of the window.

You can also capture these details when users request from Slack. We populate the time zone from Slack (or your org), so schedules land where they should.

Why it matters: Fewer standing privileges, cleaner audits, and less back-and-forth.

How to try it: From an application, enable time-based access in Application settings and then submit a request (in the product or Slack).

‍

AI imports for apps and users — from messy lists to clean CSVs

Add applications faster with AI Paste: drop a plain-text list and we convert it into a strict CSV—sanitized, validated, and ready to import. If the Owners column is blank, we default to your first administrator, and owners are now optional (we’ll still validate any emails you do include).

For users, you can upload screenshots of tables and we’ll OCR them into CSV, map the fields, and show clear, client-side validation with exact row highlights. If a mapping is tricky (think complex APIs), we automatically retry with added context—less tinkering, fewer retries.

Why it matters: Imports that used to take an hour now take minutes, with instant feedback when something’s off.

How to try it:

• Applications → Import and select AI Paste or CSV.
• People → Import and upload a CSV or screenshot.

/ima

HRIS: bulk actions, better previews, and smarter mapping

The HRIS employee table now includes search, sorting, and filters (unmapped, starting soon, leaving soon). You can bulk create, bulk map, bulk remove, and bulk unmap people directly from the table. Sync banners and status messages are clearer, and the table auto-refreshes when a sync completes—no page reloads needed.

We also made mapping smarter: HRIS syncs always map employees to existing users when emails match, even if you haven’t set filters yet. And when HRIS is your people source, we sync core and custom fields regardless of filters to keep records accurate.

Why it matters: Faster clean-up, fewer manual steps, and up-to-date people data.

How to try it: Go to People → Employees (or your HRIS integration) to review, filter, and take bulk actions.

Approvals & audits — clearer groups, quicker triage

Approvals are easier to design and easier to read:

• Approval Groups replace the older owners approach. Mix technical owners, groups, or individuals and drag-and-drop to order them.
• The Access Requests table is sortable again, so you can quickly triage by time, requester, app, or status.
• We’ve improved how we display who responded (including system-run automations) and when, so audits tell a complete story.
• Slack and Teams notifications now try all recipients even if one fails—fewer silent misses.

Why it matters: Faster approvals with less ambiguity and cleaner audit trails.

How to try it: Open any app’s Approvals section to configure; triage in Access → Requests.

Integrations, reliability, and branding — fewer surprises, more polish

We shipped a long list of improvements that reduce friction and make state visible:

• Integration management: A cleaner experience for configuring integrations, with clearer error messages and warnings when switching types. OAuth is more reliable (popup hand-off + timeouts), and there’s a new API Key auth option for services that require Authorization: ApiKey ….
• Pagination that just works: GraphQL cursors, offset/number paginators with repeat-detection, start-page controls, and friendlier limits for services with caps (e.g., when a provider only returns 50 per page). This also hardens SCIM imports that don’t follow specs perfectly.
• Sync visibility: Directory cards now show syncing status and sensible “last sync” times. Provisioning banners are clearer, and tables auto-refresh after imports complete.
• Service accounts: You can label application accounts as non-human (service/bot). This helps identity mapping and reviews focus on real users.
• Branding: Your logo and dark navigation now display correctly on the first visit to your login page.
• Housekeeping: Accepted app invites no longer linger as “pending,” and non-admin assignees on app tasks can view the app details they need to complete their work.

Why it matters: Less setup ambiguity, sturdier syncs, and a UI that reflects reality.

Admin tips

• Separate humans from bots: Mark known service accounts as non-human so reviews and “unmapped” counts stay accurate.
• Use scheduled access for sensitive roles: Require a duration and start time—especially helpful when approvals happen in Slack.

Closing

Our goal is simple: save you time while reducing risk. With scheduled access, AI-assisted imports, bulk HRIS actions, and clearer approvals, YeshID helps you run identity and access with confidence.

Have feedback or want to see a quick demo? Drop us a note—we’d love to hear what would save your team the most time next.

‍