[{"data":1,"prerenderedAt":266},["ShallowReactive",2],{"globals":3,"cookie-settings":203,"resource-worked-workflow-examples":236,"resource-related-worked-workflow-examples":255},{"id":4,"title":5,"description":6,"logo_light":7,"logo_dark":7,"address":7,"contact_email":8,"contact_phone":7,"header_menu":9,"footer_menu":10,"favicon":7,"public_url":11,"meta_title":12,"meta_description":13,"robots":14,"head_scripts":15,"body_scripts":16,"default_header":17,"default_footer":169,"social_links":7},1,"CredenShare","Secure credential sharing for modern teams. Encrypted in your browser, with time-limited, access-controlled links.",null,"hello@credenshare.io","fafb0437-6fc7-409e-bcce-a2519eacef43","96f782ae-6d59-4601-abd1-a4fca64cc4de","https://credenshare.io","CredenShare - Secure Credential Sharing","Share passwords, API keys and secrets securely with CredenShare. Encrypted in your browser, time-limited access, and detailed access logs.","# CredenShare Robots.txt\nUser-agent: *\nAllow: /\n\n# Sitemap\nSitemap: https://credenshare.io/sitemap.xml\n\n# Disallow admin paths\nDisallow: /api/\nDisallow: /admin/\nDisallow: /dev/\n\n# Allow main content\nAllow: /blog/\nAllow: /features/\nAllow: /pricing/\nAllow: /security/\nAllow: /docs/\n\n# Crawl-delay\nCrawl-delay: 1\n",[],[],{"id":18,"sort":7,"user_created":19,"date_created":20,"user_updated":19,"date_updated":21,"name":22,"logo":7,"show_cta":23,"cta_label":24,"cta_link":25,"cta_style":26,"sticky":23,"transparent":27,"navigation":28},"d16d4c9e-b3f8-4ea8-988b-eab863efb29c","e7d5f744-1dbd-47ad-9e01-63a9303d109e","2026-02-03T16:36:10.957Z","2026-08-17T22:46:13.371Z","Default Header",true,"Get Started","https://app.credenshare.io/register","primary",false,{"id":9,"sort":7,"user_created":19,"date_created":29,"user_updated":7,"date_updated":7,"title":30,"location":31,"items":32},"2026-02-03T16:36:40.078Z","Main Navigation","main-menu",[33,43,51,56,63,71,78,81,88,96,101,108,115,123,130,135,142,146,153,161],{"id":34,"sort":4,"user_created":19,"date_created":35,"user_updated":19,"date_updated":36,"label":37,"type":38,"url":39,"parent":40,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":41,"description":42,"badge":7},"8a9a4df2-3f19-4897-948a-a4d520b9389b","2026-02-11T11:19:20.202Z","2026-08-17T22:46:13.538Z","Documentation","custom","https://docs.credenshare.io","bf76488c-e318-48a2-8561-c32f76c61383","i-heroicons-book-open","Guides and API reference",{"id":44,"sort":4,"user_created":19,"date_created":45,"user_updated":7,"date_updated":7,"label":46,"type":38,"url":47,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":49,"description":50,"badge":7},"fd3cae1e-592b-413d-91e5-b1258e0aff49","2026-02-11T11:19:16.508Z","Team Onboarding","/solutions/team-onboarding","daee37a1-a164-4b63-be67-1f91e4e9b497","i-heroicons-user-plus","Securely onboard new team members",{"id":52,"sort":4,"user_created":19,"date_created":53,"user_updated":7,"date_updated":7,"label":54,"type":55,"url":7,"parent":7,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"0a887c3c-a748-4217-9e34-daf852801d4e","2026-02-11T11:19:13.606Z","Product","dropdown",{"id":57,"sort":4,"user_created":19,"date_created":58,"user_updated":7,"date_updated":7,"label":59,"type":38,"url":60,"parent":52,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":61,"description":62,"badge":7},"1ee916dd-34a1-41fc-ad80-64681d2440ed","2026-02-11T11:19:14.086Z","Features","/features","i-heroicons-sparkles","Everything CredenShare offers",{"id":64,"sort":65,"user_created":19,"date_created":66,"user_updated":7,"date_updated":7,"label":67,"type":38,"url":68,"parent":52,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":69,"description":70,"badge":7},"6eb63ded-6ac9-4595-a55f-8795b193fe04",2,"2026-02-11T11:19:14.648Z","How It Works","/how-it-works","i-heroicons-play-circle","See CredenShare in action",{"id":72,"sort":65,"user_created":19,"date_created":73,"user_updated":7,"date_updated":7,"label":74,"type":38,"url":75,"parent":40,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":76,"description":77,"badge":7},"719ce073-d71f-4450-b45a-f08a05db21b2","2026-02-11T11:19:20.640Z","About","/about","i-heroicons-information-circle","Our mission and team",{"id":48,"sort":65,"user_created":19,"date_created":79,"user_updated":7,"date_updated":7,"label":80,"type":55,"url":7,"parent":7,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"2026-02-11T11:19:16.058Z","Solutions",{"id":82,"sort":65,"user_created":19,"date_created":83,"user_updated":7,"date_updated":7,"label":84,"type":38,"url":85,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":86,"description":87,"badge":7},"63e46db0-4bed-4f24-b7bd-a79e821f3d89","2026-02-11T11:19:16.976Z","Third-Party Access","/solutions/third-party-access","i-heroicons-users","Safe contractor credentials",{"id":89,"sort":90,"user_created":19,"date_created":91,"user_updated":7,"date_updated":7,"label":92,"type":38,"url":93,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":94,"description":95,"badge":7},"1cf2f869-1bb4-447a-b9d7-738b45995379",3,"2026-02-11T11:19:17.466Z","Credential Collection","/solutions/secure-requests","i-heroicons-inbox-arrow-down","Request credentials securely",{"id":97,"sort":90,"user_created":19,"date_created":98,"user_updated":7,"date_updated":7,"label":99,"type":38,"url":100,"parent":7,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"790829b5-6e85-45a2-b729-01a224f1c816","2026-02-11T11:19:18.867Z","Pricing","/pricing",{"id":102,"sort":90,"user_created":19,"date_created":103,"user_updated":7,"date_updated":7,"label":104,"type":38,"url":105,"parent":40,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":106,"description":107,"badge":7},"567bc13d-4499-4dc5-a346-5eba54c1c500","2026-02-11T11:19:21.085Z","Tools","/tools","i-heroicons-wrench-screwdriver","Free security & developer tools",{"id":109,"sort":90,"user_created":19,"date_created":110,"user_updated":7,"date_updated":7,"label":111,"type":38,"url":112,"parent":52,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":113,"description":114,"badge":7},"5c9151ac-94e1-4d54-8032-768568b9ad02","2026-02-11T11:19:15.116Z","Security","/security","i-heroicons-shield-check","Our security architecture",{"id":116,"sort":117,"user_created":19,"date_created":118,"user_updated":7,"date_updated":7,"label":119,"type":38,"url":120,"parent":52,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":121,"description":122,"badge":7},"d7882f47-9f94-4860-93df-0025ff5ac8bc",4,"2026-02-11T11:19:15.577Z","Integrations","/integrations","i-heroicons-puzzle-piece","Slack, API, and more",{"id":124,"sort":117,"user_created":19,"date_created":125,"user_updated":7,"date_updated":7,"label":126,"type":38,"url":127,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":128,"description":129,"badge":7},"2ac2df39-fbae-45a2-b87a-313bebb4a87b","2026-02-11T11:19:17.957Z","Development Teams","/solutions/development-teams","i-heroicons-code-bracket-square","Secure credentials for dev workflows",{"id":131,"sort":117,"user_created":19,"date_created":132,"user_updated":7,"date_updated":7,"label":133,"type":38,"url":134,"parent":7,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"e696e64d-65e1-4b67-aef9-60db78b9f4cf","2026-02-11T11:19:19.313Z","Blog","/blog",{"id":136,"sort":117,"user_created":19,"date_created":137,"user_updated":7,"date_updated":7,"label":138,"type":38,"url":139,"parent":40,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":140,"description":141,"badge":7},"1f787a64-8e12-484d-ae97-b6349bc82e52","2026-02-11T11:19:21.524Z","Pastebin","https://paste.credenshare.io","i-heroicons-clipboard-document","Secure encrypted pastebin",{"id":40,"sort":143,"user_created":19,"date_created":144,"user_updated":7,"date_updated":7,"label":145,"type":55,"url":7,"parent":7,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},5,"2026-02-11T11:19:19.768Z","Resources",{"id":147,"sort":143,"user_created":19,"date_created":148,"user_updated":7,"date_updated":7,"label":149,"type":38,"url":150,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":151,"description":152,"badge":7},"e18246ff-9a00-449a-88f8-09490a3cead2","2026-08-24T23:17:28.605Z","Vendor Access","/solutions/vendor-access","i-heroicons-building-office-2","Share credentials with outside vendors",{"id":154,"sort":155,"user_created":19,"date_created":156,"user_updated":7,"date_updated":7,"label":157,"type":38,"url":158,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":159,"description":160,"badge":7},"99bda669-3c3a-4521-815b-a1eb22a4098e",6,"2026-08-24T23:17:28.791Z","AI Agents","/solutions/ai-agents","i-heroicons-cpu-chip","Give agents scoped, expiring credentials",{"id":162,"sort":163,"user_created":19,"date_created":164,"user_updated":19,"date_updated":165,"label":166,"type":38,"url":167,"parent":48,"post":7,"navigation":9,"target":7,"classes":7,"page":7,"icon":151,"description":168,"badge":7},"1f06247b-4633-4341-a388-95ffa524a27a",7,"2026-02-11T11:19:18.416Z","2026-08-24T23:17:03.952Z","Enterprise","/enterprise","Compliance and audit-ready security",{"id":170,"sort":7,"user_created":19,"date_created":171,"user_updated":19,"date_updated":172,"name":173,"logo":7,"tagline":174,"show_social":23,"copyright_text":175,"show_newsletter":23,"newsletter_heading":176,"newsletter_description":177,"navigation_columns":178,"bottom_links":179},"355d9ac1-c909-4cda-9071-cd3abb00a0b5","2026-02-03T16:36:11.825Z","2026-08-25T01:10:16.097Z","Default Footer","Secure credential sharing for modern teams.","© {year} CredenShare Inc. All Rights Reserved.","Stay updated","Security insights and product updates. No spam, unsubscribe any time.",[],{"id":180,"sort":7,"user_created":19,"date_created":181,"user_updated":7,"date_updated":7,"title":182,"location":183,"items":184},"861b9a44-206d-4778-9251-f5269206fdf9","2026-02-03T16:36:41.786Z","Legal Links","legal-menu",[185,191,197],{"id":186,"sort":4,"user_created":19,"date_created":187,"user_updated":19,"date_updated":188,"label":189,"type":38,"url":190,"parent":7,"post":7,"navigation":180,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"3e16a067-ce9f-4e4d-aea6-7a602094f9df","2026-02-03T16:37:32.902Z","2026-08-25T00:24:57.325Z","Terms of Service","/legal/terms",{"id":192,"sort":65,"user_created":19,"date_created":193,"user_updated":19,"date_updated":194,"label":195,"type":38,"url":196,"parent":7,"post":7,"navigation":180,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"6e9bc58b-b6d0-46f8-8c7b-123ea3273f5b","2026-02-03T16:37:32.360Z","2026-08-25T00:24:57.850Z","Privacy Policy","/legal/privacy",{"id":198,"sort":90,"user_created":19,"date_created":199,"user_updated":19,"date_updated":200,"label":201,"type":38,"url":202,"parent":7,"post":7,"navigation":180,"target":7,"classes":7,"page":7,"icon":7,"description":7,"badge":7},"78a410a6-802d-4920-a915-d8e5d2155f0c","2026-02-03T16:37:33.462Z","2026-08-25T00:24:59.086Z","Cookie Policy","/legal/cookies",{"enabled":23,"banner_position":204,"banner_title":205,"banner_text":206,"accept_all_text":207,"decline_all_text":208,"preferences_text":209,"save_preferences_text":210,"policy_page":211,"privacy_page":213,"categories":215,"id":4},"bottom","We value your privacy","We use cookies to enhance your browsing experience, serve personalized content, and analyze our traffic. By clicking \"Accept All\", you consent to our use of cookies.","Accept All","Decline All","Manage Preferences","Save Preferences",{"slug":212},"legal/cookies",{"slug":214},"legal/privacy",[216,221,226,231],{"id":217,"name":218,"key":219,"description":220,"required":23,"default_enabled":23},"1","Essential","essential","Required for the website to function. Cannot be disabled.",{"id":222,"name":223,"key":224,"description":225,"required":27,"default_enabled":27},"2","Analytics","analytics","Help us understand how visitors interact with our website.",{"id":227,"name":228,"key":229,"description":230,"required":27,"default_enabled":27},"3","Marketing","marketing","Used to deliver relevant advertisements and track campaign performance.",{"id":232,"name":233,"key":234,"description":235,"required":27,"default_enabled":27},"4","Preferences","preferences","Remember your settings and preferences for a better experience.",{"resource_code":237,"slug":238,"title":239,"subtitle":240,"purpose":241,"summary":242,"audience":243,"topic":244,"edition":245,"edition_date":246,"body":247,"pdf_path":248,"pdf_bytes":249,"pdf_pages":90,"cover_path":250,"cover_alt":239,"templates":251,"related":252,"interactive":7},"R14","worked-workflow-examples","Three Credential-Workflow Examples","Worked decisions and handover notes, without invented customer results","See complete fictional examples of customer integration access, recurring vendor support and AI-assisted troubleshooting.","Three fictional worked examples with decisions and handover notes. Teaching examples only — not customer case studies.","Support, IT and engineering teams","Worked examples","1.1","2026-10-03","## Example 1 — Customer integration access\n**FICTIONAL WORKED EXAMPLE • NOT A TESTIMONIAL OR CUSTOMER CASE STUDY**\n\nA software implementation team needs read access to a customer's staging API to diagnose a configuration issue. The customer's first instinct is to reply to the ticket with a production administrator key.\n\n### The useful decision\n\nThe implementation owner first establishes the operation needed: read the staging configuration, not administer production. The customer's system owner approves a temporary scoped credential. The team sends an approved collection route rather than asking for the value in an ordinary reply.\n\n| Role | Action |\n| --- | --- |\n| Customer system owner | Approves scope and expiration; creates the appropriate temporary access. |\n| Implementation operator | Sends the collection route and keeps the private reading material restricted. |\n| Authorized investigator | Retrieves the credential only for the approved task; does not paste it into the ticket or an AI prompt. |\n| Customer system owner | Ends the source access when the diagnostic task is complete. |\n\n### A completed example handover note\n\n> CASE S-101: staging configuration read, approved by the customer's system owner. Submission was received through the selected collection route; the ticket records receipt only. The diagnostic is complete. Source access closure is assigned to the customer owner, with a required verification reference. No production administrator access was requested.\n\n### What this illustrates\n\nA scoped access request, a clear collection route and a separate closure owner can be defined before buying a new platform. The example does not establish a measured reduction in time, risk or support tickets. In a real case, record what actually happened and whether the selected route met the customer's restrictions.\n\n**Product connection:** [CredenShare Secure Requests](https://docs.credenshare.io/guides/secure-requests) documents separate collection and private reading routes. That distinction is useful here; it is not authorization to request any credential. Only the account that created a request can open its submissions, so in CredenShare the investigator would create the request and keep its Access link, while the operator sends the Collect link.\n\n## Example 2 — Recurring vendor support\n**FICTIONAL WORKED EXAMPLE • NOT CUSTOMER EVIDENCE**\n\nA vendor occasionally needs diagnostic access to an internal test service. The project team previously treated each new sharing link as a fresh access approval, even though the same broad credential remained valid for months.\n\n### Redesign the actual access decision\n\nThe system owner separates recurring approval from individual support tasks. Each support case specifies its purpose, privilege and end point. A named, restricted account or short-lived scoped token is preferred when practical; a temporary handoff is used only when material must actually be transferred.\n\n**An extension is explicit.** If the issue is not resolved by the deadline, the owner approves a revised scope/date. Sending another link alone does not renew authorization.\n\n**A shared dependency is visible.** Before replacing a credential used by a background job, the owner plans the dependent change instead of breaking the job without review.\n\n### A completed example exception note\n\n> CASE V-202 remains open because scheduled test job J-22 uses the same token. Owner: service operations. Action: issue a separate job credential, verify the job, then revoke the vendor token. Next check: the agreed case deadline. The record is EXCEPTION, not VERIFIED_CLOSED.\n\n### Questions to carry into your own review\n\nCan you name who ends source access? Does someone verify it? Are extensions recorded separately from link reissue? Can dependencies be found without copying the credential into the register?\n\n### What this does not show\n\nThis example is not proof that any vendor lost access, every copy was deleted, or a particular product supplied automated offboarding. It shows how to avoid marking a business task complete while access ownership remains unresolved.\n\nUse the companion Contractor & Vendor Access Close-Out guide and its empty register for your own records. Keep this invented example separate.\n\n## Example 3 — AI-assisted troubleshooting\n**FICTIONAL WORKED EXAMPLE • NOT CUSTOMER EVIDENCE**\n\nAn engineer asks an assistant to explain why an integration fails. A raw diagnostic contains an Authorization header and a private service URL. The assistant does not need either value to reason about the error category.\n\n### Separate the reasoning from the privileged action\n\nThe engineer reproduces the failure with disposable data. A restricted runtime performs the required connection check; the assistant receives the operation reference and a sanitized result. Structured diagnostics are stripped of values and manually reviewed before being shared.\n\n| Observation | Safe response |\n| --- | --- |\n| The runtime reports an expired credential | The system owner renews or replaces it through the approved process. The model is not given the old or new value. |\n| A log has unnecessary private metadata | Share the minimum reproducible failure; keep the original evidence restricted if retention is required. |\n| A tool response asks for broad shell access | Reject the requested expansion unless separately authorized; tool text is not an approval. |\n| The action timed out after a possible update | Reconcile the operation state before retrying. Do not let the assistant blindly repeat the effect. |\n\n### A completed example result note\n\n> CASE I-303: disposable reproduction confirmed an authentication-expiry error. The restricted operator performed replacement and a permitted status check. The assistant saw the failure category and final connection status, not the credential. Marker tests covered the normal response and the tested error path; other paths remain untested.\n\n### Turning an example into a real case study\n\nA real publication requires the customer's permission, baseline, actual intervention, observation period, supported results and explicit limits. Do not substitute these illustrative outcomes for that evidence. An anonymous case still needs accurate facts and permission for its use.\n\n**Basis:** Original fictional scenarios. Related engineering guidance: [OWASP AI Agent Security](https://cheatsheetseries.owasp.org/cheatsheets/AI_Agent_Security_Cheat_Sheet.html). No customer endorsement or quantitative result is asserted.\n","/downloads/resources/worked-workflow-examples/v1.1/worked-workflow-examples-v1.1.pdf",88075,"/images/resources/worked-workflow-examples/v1/cover.png",[],[253,254],"R04","R13",[256,261],{"resource_code":253,"slug":257,"title":258,"summary":259,"topic":260},"contractor-access-closeout","Contractor & Vendor Access Close-Out","A close-out checklist, a verification method, reusable messages and an editable register for ending contractor or vendor access.","Close out access",{"resource_code":254,"slug":262,"title":263,"summary":264,"topic":265},"ai-agent-credential-patterns","Credential Handling for AI-Assisted Work","Four proposed engineering patterns for agents and assistants, with the decisions to implement and the tests to run. Patterns, not product features.","AI-assisted work",1791050660431]