[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"productUpdate-en::routine-approval-modes-and-change-history:en":3,"productUpdatesNearDate-en:timestamp-2026-11-06T16:00+09:00:en":20},{"id":4,"title":5,"slug":6,"description":7,"body":8,"tags":9,"coverUrl":13,"coverMediaUrl":14,"ogImageUrl":14,"createdAt":15,"updatedAt":16,"datePublished":17,"locale":18,"updateType":19},"3X8q0I6oursr0m8FOlxIJ3","Approval Modes and Change History for Routines","routine-approval-modes-and-change-history","Choose an approval mode for each routine to control writes and deletions in scheduled runs, and see who changed a routine and when in its change history.","\u003Cp>You can now choose an approval mode for each routine. Decide per routine how far scheduled runs may go with writes to external services and deletions, so you can hand work over to routines with confidence. We have also added a change history that shows who changed a routine's settings and when.\u003C\u002Fp>\u003Cp>A routine run doesn't wait for confirmation. Operations that would need confirmation in a chat are skipped, and Codatum Agent continues the run without them.\u003C\u002Fp>\u003Ch2>Key features\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>\u003Cb>Approval mode for each routine\u003C\u002Fb>: In the routine editor, choose \u003Cb>Manual\u003C\u002Fb>, \u003Cb>Auto\u003C\u002Fb>, or \u003Cb>Allow all\u003C\u002Fb> under \u003Cb>Approval mode\u003C\u002Fb>. With \u003Cb>Auto\u003C\u002Fb>, writes to external services and deletions run only if they are in \u003Cb>Allowed without asking\u003C\u002Fb>, and other operations run without restriction\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cb>Allow skipped operations next time\u003C\u002Fb>: Operations skipped in a run are listed under \u003Cb>Not allowed\u003C\u002Fb> in the run history. Click \u003Cb>Allow next time\u003C\u002Fb> to add an operation to \u003Cb>Allowed without asking\u003C\u002Fb> so it runs from the next run\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cb>Track changes with change history\u003C\u002Fb>: The \u003Cb>Change history\u003C\u002Fb> tab lists when, by whom, and how (such as \u003Cb>Edited in the editor\u003C\u002Fb>, \u003Cb>From a conversation\u003C\u002Fb>, or \u003Cb>Allowed from a run\u003C\u002Fb>) the name, instructions, schedule, AI profile, approval settings, and other settings were changed\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cb>Compare with the previous save\u003C\u002Fb>: Select a row in the change history to see which items changed since the previous save\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Example use cases\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>For a routine that writes to external services through agent connectors, add only the operations it needs to \u003Cb>Allowed without asking\u003C\u002Fb> and skip all other writes\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Run a new routine in \u003Cb>Auto\u003C\u002Fb>, review the operations it skipped in the run history, and allow only the ones you need\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>When the results of a routine shared by several people change, check the change history for recent edits to its instructions or schedule\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Related documentation\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.codatum.com\u002Ffeatures\u002Fai-agent\u002Froutines#approval\" target=\"_blank\" rel=\"noopener noreferrer\">Routine approval\u003C\u002Fa>\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.codatum.com\u002Ffeatures\u002Fai-agent\u002Froutines#results\" target=\"_blank\" rel=\"noopener noreferrer\">Reviewing results\u003C\u002Fa>\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.codatum.com\u002Ffeatures\u002Fai-agent\u002Froutines#change-history\" target=\"_blank\" rel=\"noopener noreferrer\">Change history\u003C\u002Fa>\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Availability\u003C\u002Fh2>\u003Cp>Routines are an optional feature and may not be available depending on your contract.\u003C\u002Fp>\u003Cp>New routines use \u003Cb>Auto\u003C\u002Fb> (routines created in a chat use that session's approval mode unless you specify one). Existing routines stay on \u003Cb>Allow all\u003C\u002Fb>. Routines don't use the chat's approval mode or \u003Cb>Allowed without asking\u003C\u002Fb>; each routine uses its own settings. Changes take effect from the next run. Only the routine's owners can use \u003Cb>Allow next time\u003C\u002Fb>.\u003C\u002Fp>\u003Cp>Anyone who can view a routine can see its change history. Pausing, resuming, and sharing are not recorded, and you cannot restore a previous version.\u003C\u002Fp>",[10],{"id":11,"name":12},"new_feature","New Feature","","https:\u002F\u002Fimages.ctfassets.net\u002Fggtw2zqmifs5\u002F6hvylFUMDLTlaJptVI6kPt\u002F782e58d1bc8859345bd52d3c8c8574fb\u002Fproduct-update-routine-approval-modes-and-change-history.png","2026-11-06T06:41:41.730Z","2026-11-06T07:00:16.172Z","2026-11-06T16:00+09:00","en","standard_release",[21,35],{"id":22,"title":23,"slug":24,"description":25,"body":26,"tags":27,"coverUrl":13,"coverMediaUrl":31,"ogImageUrl":31,"createdAt":32,"updatedAt":32,"datePublished":33,"locale":18,"updateType":34},"43MDvToE5X5RTZYXF909Xs","IP Access Control and Workspace-Wide MFA Enforcement Are Now Generally Available","ip-access-control-and-workspace-mfa-ga","IP access control and workspace-wide MFA enforcement, previously in beta, are now generally available for production use.","\u003Cp>IP access control and workspace-wide multi-factor authentication (MFA) enforcement, previously in beta, are now generally available. You can now control which networks members can access Codatum from and how they sign in.\u003C\u002Fp>\u003Ch2>Key features\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>IP access control: Restrict access to the Codatum admin console to allowed IP addresses, such as your corporate network or VPN.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>MFA enforcement: Require MFA for every member of a workspace. Members can use an authenticator app (Google Authenticator or Microsoft Authenticator) or SMS.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Cp>* This feature is available on the Enterprise plan.\u003Cbr>* Public links are not subject to IP access control.\u003C\u002Fp>",[28],{"id":29,"name":30},"update-news","Update News","https:\u002F\u002Fimages.ctfassets.net\u002Fggtw2zqmifs5\u002F4pYALLYrl5fU6g6oTWkA9q\u002F95ed7a72d41b52cedf58fde2f6a20bf0\u002FCleanShot_2025-03-23_at_21.09.56_2x.jpeg","2026-11-05T07:00:10.797Z","2026-11-05T16:00+09:00","major_release",{"id":36,"title":37,"slug":38,"description":39,"body":40,"tags":41,"coverUrl":13,"coverMediaUrl":43,"ogImageUrl":43,"createdAt":44,"updatedAt":44,"datePublished":45,"locale":18,"updateType":34},"1SFS2vHvFsB746GfcmIctO","Custom Roles Are Now Available in Beta","custom-roles-beta","Build your own workspace roles by choosing a permission level for each area, and assign them to users and service accounts. Now available in beta.","\u003Cp>Custom roles are now available in beta, so you can build your own workspace roles. Choose a permission level for each area, such as workspace, connections, and notebooks, and assign roles that match how your team divides responsibilities to users and service accounts.\u003C\u002Fp>\u003Cp>Until now, workspace roles were limited to the built-in roles. With custom roles, you can create roles such as Editor permissions plus some management permissions, or view-only access to just the areas a person needs.\u003C\u002Fp>\u003Ch2>Key features\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>\u003Cb>Choose a level for each area\u003C\u002Fb>: For each item, such as Workspace settings, Members, Workspace connections, Workspace notebooks, and Workflows, select \u003Cb>None\u003C\u002Fb> or one of its levels (such as \u003Cb>View\u003C\u002Fb>, \u003Cb>Run\u003C\u002Fb>, \u003Cb>Edit\u003C\u002Fb>, or \u003Cb>Publish\u003C\u002Fb>). A higher level includes the lower levels\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cb>Start from a template\u003C\u002Fb>: In \u003Cb>Workspace settings\u003C\u002Fb> > \u003Cb>Roles\u003C\u002Fb>, click \u003Cb>New role\u003C\u002Fb> and choose \u003Cb>Blank role\u003C\u002Fb> or \u003Cb>Start from Editor\u003C\u002Fb>. You can also \u003Cb>Duplicate\u003C\u002Fb> an existing custom role as the basis for a new one\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cb>Grant connections one by one\u003C\u002Fb>: You can now grant resource roles on individual connections whose access level is Workspace. Even with \u003Cb>Workspace connections\u003C\u002Fb> set to \u003Cb>None\u003C\u002Fb>, you can let a role use only the connections it needs\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Cb>Manage guest invitations with roles\u003C\u002Fb>: Whether someone can invite guests from a report is now decided by the \u003Cb>Guest invitations\u003C\u002Fb> permission of their role. The setting that removes guest invitations from the built-in Editor role has moved to the Editor's \u003Cb>Permissions\u003C\u002Fb> on the \u003Cb>Roles\u003C\u002Fb> page\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Example use cases\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>Let your data platform team keep Editor permissions and also create and manage connections\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Give executives or members of other departments a role that can only view the notebooks they need\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>When departments use different data warehouses, give each department access only to its own workspace connections\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Related documentation\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.codatum.com\u002Fworkspace\u002Faccess-and-security\u002Froles#custom-role\" target=\"_blank\" rel=\"noopener noreferrer\">Custom roles\u003C\u002Fa>\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.codatum.com\u002Fworkspace\u002Faccess-and-security\u002Froles#permissions-connection\" target=\"_blank\" rel=\"noopener noreferrer\">Connection permissions\u003C\u002Fa>\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>\u003Ca href=\"https:\u002F\u002Fdocs.codatum.com\u002Fworkspace\u002Faccess-and-security\u002Froles#editor-guest-invite\" target=\"_blank\" rel=\"noopener noreferrer\">Changing guest invitations for Editor\u003C\u002Fa>\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Availability\u003C\u002Fh2>\u003Cp>Custom roles are an optional feature in beta and may not be available depending on your contract. The specification might change without notice.\u003C\u002Fp>\u003Cp>Only workspace owners can create, edit, and delete roles. Permissions reserved for workspace owners, such as deleting the workspace, granting the owner role, and API keys, cannot be included in a custom role. Custom roles cannot be assigned to guests or to users who join through allowed domains or invite links. Users with a custom role count toward the number of editors, regardless of their permissions.\u003C\u002Fp>",[42],{"id":11,"name":12},"https:\u002F\u002Fimages.ctfassets.net\u002Fggtw2zqmifs5\u002F6qTGCKqaStct7a9h58qrMS\u002Fc65b21ecab3cc06ee1b0ceea6a7c0ac4\u002Fproduct-update-custom-roles-beta.png","2026-11-03T23:00:17.584Z","2026-11-04T08:00:00+09:00"]