Employee documents may be uploaded and published to shared spaces
Source references: 3The instructions upload onboarding documents to shared Drive and then announce a new hire by sharing their profile document in Chat. They do not require checking the document, folder permissions, Chat membership, employee consent, or minimum necessary disclosure. The protection provided by `--sanitize` is also unspecified.
If a document contains an address, phone number, personal email, identity information, compensation, or other HR data, choosing the wrong folder or Chat space could give unauthorized people persistent access and allow further sharing.
The skill uploads onboarding files to a shared Drive folder and shares a new hire's profile document in a Chat space. If folder or space membership is too broad, employee information could reach people who do not need it. Although `--sanitize` is required for PII-sensitive operations, the source does not define which fields it removes or require permission, consent, or minimum-disclosure checks. Users can ask the author to define sanitization and restrict the destination and shared fields.
- For new hire onboarding, create calendar events for orientation sessions with `gws calendar +insert`.- Upload onboarding docs to a shared Drive folder with `gws drive +upload`.- Announce new hires in Chat spaces with `gws workflow +file-announce` to share their profile doc.- Convert email requests into tracked tasks with `gws workflow +email-to-task`.Show 2 other places
## Tips- Always use `--sanitize` for PII-sensitive operations.- Create a dedicated 'HR Onboarding' calendar for tracking orientation schedules.- Upload onboarding docs to a shared Drive folder with `gws drive +upload`.- Announce new hires in Chat spaces with `gws workflow +file-announce` to share their profile doc.- Convert email requests into tracked tasks with `gws workflow +email-to-task`.