It seems the title is not entirely clear but give this tip a chance. Once used, you will see immediate benefits when collaborating with others on Google Drive .
Download Google Drive for iOS
Download Google Drive for Android
It's easy to make a copy of any document in your Google Drive account. But what if you want your collaborators to automatically create copies when they receive the sharing link? This tip can be useful when you want to protect an original document or template, while allowing others the flexibility to edit a copy of the document for themselves.
The typical case is a Google Doc document that needs to be completed individually. Collaborators can enter details into copies of documents without damaging the originals.
You won't have to ask them to make a copy manually, just follow the steps below and the copy will be created automatically for each recipient. This tip works well for all Google Drive tools: Docs, Sheets and Slides .
Step 1 : Open the Google Drive document you want to share. Click the blue Share button at the top right of the document.
Step 2 : In the Share with others dialog box , click the Get shareable link icon . Set sharing settings to Edit to update the link. Copy the link to your email or any other means of exchange.
Step 3 : Alternatively, click on Advanced . Uncheck the Notify people box . You do not want them to receive email notifications for shared files. You want to send links to documents that can be shared separately. Click OK to save the changes.
Step 4 : Copy and paste the shared link in an email. Now delete everything after the forward slash in the link and insert the copy .
Email and job done. Recipients who click on the link will be taken to the Google Drive screen that prompts them to make a copy of the document.
When clicking Make a copy , a local copy of the document is saved in their Google Drive. The original still exists intact in your account.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
