Connect Sesame
Connect Sesame with a company API token, choose which HR information Gurusup reads, see how often it refreshes, and fix a token Sesame refuses.
Admins only. Gurusup learns your company structure and time-off rules from Sesame and, if you turn it on, who is out and when, so you can ask "Who from the rollout team is out today, and which Linear issues are assigned to them?" and get Sesame joined with your issues. Gurusup only reads Sesame and adds nothing there.
At a glance
| Topic | Details |
|---|---|
| Who can connect | Admins |
| What you need | A Sesame company API token, created by a Sesame administrator |
| What Gurusup reads | The areas you choose: Organization, Time policies and Who's out |
| How changes arrive | Gurusup reads who is out every 30 minutes and everything else every 6 hours |
| Past content | None. Sesame has no Import history. |
| Knowledge access | Default access, Restricted or Private. See Who can read it. |
Before you start
- You are an admin in Gurusup.
- In Sesame, only a Sesame administrator sees Ajustes > Integraciones > API, where the token is created.
- The token must be a company token. Sesame takes one connection per company in each Gurusup organization.
- Gurusup starts from the moment you connect and cannot import earlier time off. See How changes arrive.
Employee records and time off are personal data about your team. Restrict the source before you connect if only some people should read them.
Connect Sesame
Open the Sesame connector
In the sidebar, open Sources, then Catalog, find Sesame (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect Sesame for the organization opens.
Choose who can read it
In the dialog, under Who can read it, keep Default access, or choose Restricted or Private from Access mode and pick the people.
Create the token
In the dialog, click Show steps below the fields and follow them: in Sesame, open Ajustes > Integraciones > API, then choose Crear nuevo token and copy it.
Paste it and choose what to read
Paste the token in API token (the hint reads "Starts with eyJ"). Tick the areas Gurusup may read, see What you choose. Gurusup says "Checking this Sesame token…" and then shows the company name with its counts: "Employees", "Holiday calendars", "Absence types", "Vacation calendars" and "Absence calendars". If Sesame does not count them within 10 seconds, the counts are replaced by "Counting is taking too long right now, usually because the company is large. You can still connect." Connect stays off until the check passes.
Connect
Click Connect. A message says "Sesame connected."
What you choose
| Area | On by default | What it covers |
|---|---|---|
| Organization | Yes | Employees, teams, offices, roles and managers |
| Time policies | Yes | Holiday calendars, absence types, vacation rules and agreements |
| Who's out | No | Vacation and absence days per person, without the reason |
To change this later, open the Sesame page and tick or untick the areas under Content. Each change saves at once, and a message says "Sesame reading choices saved." Unticking an area withdraws what it brought in, and ticking it again brings it back at the next read.
What Gurusup reads
| Area | Document | What it holds |
|---|---|---|
| Organization | One per employee | The profile fields Sesame returns for the employee, except the ones Gurusup never reads, with their managers, departments and offices |
| Organization | One for the company structure | Departments, offices, roles and levels, and which employees belong to which department and office |
| Time policies | One per holiday calendar | The calendar Sesame returns |
| Time policies | One for time-off policies | Absence types, vacation rules, agreements and workday types |
| Who's out | One per person and year, titled "Time off: name year" | Vacation days with the allowance in days, and absence days shown as "Absent" |
What Gurusup never reads
Gurusup lists it under Gurusup never reads. Gurusup drops the sensitive fields from every answer from Sesame, and it asks Sesame only for the lists in the table above.
- National ID and Social Security numbers
- Bank account and bank details
- PINs and access cards
- Disability and health details
- Salary ranges and hourly rates
- Absence reasons, comments and attached documents
- Payroll, contracts, expenses, check-ins and employee documents
How changes arrive
| What | How often Gurusup reads it |
|---|---|
| Employees, company structure, holiday calendars and time-off policies | Every 6 hours |
| Who's out | Every 30 minutes |
Sesame has no change feed, so Gurusup compares each read with the last one. When you connect, it does not import what Sesame already holds:
- A record last changed before you connected is only noted. It comes in when it changes.
- Vacation and absence days count from the day you connect up to today. Earlier days stay out, and a day booked for later comes in on the day.
- A record deleted in Sesame, or no longer listed, is withdrawn: what Gurusup learned only from it leaves, and anything other sources also back stays.
Follow each document on Follow ingestion.
Who can read it
Sesame is one source.
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
Set it when you connect and it applies before Gurusup reads anything. To change it later, open the Sesame page and change Access mode under Knowledge access; it saves as soon as you change it. What Gurusup already learned keeps the access it had. See Restrict a source to specific people.
Check that it worked
Check the badge
On Sources, open the Sesame page. Under Organization accounts, the badge reads Connected.
Change something
In Sesame, edit an office name. With Who's out on, add a vacation day for today instead.
Follow it
Open Ingest and pick the Sesame source in the filter. The change moves to Learned, within 6 hours, or within about 30 minutes for time off.
Reconnect
If Sesame stops accepting the token, the connection shows Needs reconnect. Click Reconnect on the account's row under Organization accounts.
Create a new token of the same company, paste it in the Reconnect dialog and click Reconnect. Your choices and Knowledge access stay, and the dialog shows only the token. A token from another Sesame company is refused.
Disconnect
On Sources, open the Sesame page. Under Danger zone, open the menu on Disconnect, choose Disconnect and confirm. Gurusup deletes the token it stored and what it learned stays. Gurusup added nothing in Sesame, so there is nothing to remove there, and the token stays valid until you delete it in Sesame. See Remove, disconnect and what stays.
If it does not work
These show under the token while Gurusup reads it, or after "Could not connect Sesame." when you click Connect:
| Message | What to do |
|---|---|
| "Sesame didn't accept this token. Create a new company API token in Sesame and paste it here." | Create a new company token and paste it. |
| "Sesame token does not include a supported company region. Create a new company API token in Sesame." | Use a company token, not another kind. |
| "This token belongs to a different Sesame company. Use a token from the company you're reconnecting." | Reconnect with a token of the same company. |
| "We couldn't read your Sesame company because of a problem on our side. Nothing was connected. Contact support for help." | Contact support. |
| "We couldn't finish connecting Sesame because of a problem on our side. Your existing sources are safe; contact support for help." | Contact support. |
| "We couldn't connect Sesame because of a problem on our side. Nothing was connected. Contact support for help." | Contact support. |
| "We couldn't save these Sesame reading choices because of a problem on our side. Your current choices are safe; contact support for help." | Your choices are unchanged. Try again, then contact support. |
| "Sesame connection was not found. Refresh the page and try again." | Refresh the page. |
| Information stops arriving | What to do |
|---|---|
| The badge reads Needs reconnect | See Reconnect. |
| An area is unticked | Tick it again under Content. |
| It changed before you connected | It comes in the next time it changes. |
| Ingestion paused, Demo Mode, or the item Paused on Ingest | See Connector troubleshooting. |
Still stuck? Contact support with what changed in Sesame and when.