Shaka for Google Calendar

How does domain-wide authorization benefit my organization?

• Promote Participation in Company Culture Initiatives By enabling domain-wide access, users can join Shaka connections via the click of 1 button in Slack or Teams and will start recieving Shaka Connections meetings simply. Domain-wide permissions make it simple for every employee to participate in Shaka without having to manually create accounts. Important: Shaka will never auto-enroll employees in programs without permission from a company administrator.
• Migrating from previous systems If your organization has moved from another system to Shaka for employee connection programming we can auto-enroll users who have already opted-into participating in such programs, preventing hundreds of users from having to re-register.
• Company Acquisition or Email Account Migration A handful of Shaka's clients have been acquired and want to bring Shaka with them onto their new email and calendar accounts. Authorizing domain-wide access across employee's new Calendar accounts will allow Shaka's services to continue seamlessly.

Permitting Access for Shaka

• Step 1 - As a Google Workspace administrator, go to the admin console (https://admin.google.com/).
• Step 2 - On the left hand menu, navigate to "Security" ➡️ "Access and Data Controls" ➡️ "API controls"
• Step 3 - At the bottom of the API controls page, click on "Manage Domain-Wide Delegation"
• Step 4 - In the API Clients menu click "Add New". Here you will need to paste the Shaka Application Client ID and scopes. You can reach out to our team at contact@joinshaka.com for the Shaka Client ID and scopes.
• Step 5 - Click "Authorize" and confirm that Shaka has been added as a new client with the requested scopes.

Easy Peasy! Just like that, your team is up and running with Shaka Connections!

Security

Shaka makes substantial efforts to provide a system that is protected against unauthorized access. Shaka limits the personal data that is collected and stored within Shaka to prevent reason for malicious attacks. All types of data that are collected on users is shared in the Shaka Master Service Agreement. No additional personal data are collected without permission. Billing and payment Information is not stored or processed on Shaka servers or applications, rather it is managed via Stripe for secure billing and payment processing. Shaka utilizes Microsoft and Google secure OAuth APIs for top-of-the-line user authentication to prevent unauthorized access across the Shaka platform. Additionally, client and user personal data is encrypted over the wire and at rest. In the rare case of any security breach, clients will be notified within 24 hours.

Availability

It is Shaka's duty to make certain the application is available for operation and use as committed our client the service agreements. In the past 6 months, Shaka has experienced less than 13 total hours of outages which includes planned system maintenance where prior notice provided to our clients more than 24 hours in advance.

Processing Integrity

In order to ensure complete, accurate, and timely access to the Shaka web application to its authorized users, Shaka uses enterprise-grade cloud servers to host our web application. Shaka has authorization guards in place throughout the application to verify data requests are only fulfilled to authorized users with appropriate permissions.

Confidentiality

Shaka prioritizes client confidentiality and does not sell, share or distribute Shaka client, user or usage data to any 3rd parties. Additionally, every employee and contractor of Shaka have signed non-disclosure agreements in place protecting client data during and after their employment at Shaka. Any confidential data or information regarding your account with Shaka will be securely stored, password protected and marked as confidential to mitigate any accidental exposure of confidential data.

Privacy

Personal information related to Shaka clients and users is collected, used, retained, disclosed, and destroyed in conformity with the commitments in the Shaka's privacy notice and with the criteria set forth in Generally Accepted Privacy Principles (GAPP).