From 23733973789fa251925f26940b15fe13f9846994 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Mon, 15 Mar 2021 13:25:50 -0500 Subject: [PATCH] fixing broken links in new_2.2 --- whats_new_22.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/whats_new_22.md b/whats_new_22.md index 791dde7..88502f8 100644 --- a/whats_new_22.md +++ b/whats_new_22.md @@ -31,11 +31,11 @@ By specifying a CIDR block restriction for a user, policy can be applied to limi ### Time-Based Account Restrictions -Scoped to the user, you can now specify a specific block of time during the day when applications can connect. For example, permit certain users or applications to access the system during specified business hours, or protect business operations during the busiest parts of the day from batch driven back-office applications that could adversely impact the system when run at the wrong time. +Scoped to the user, you can now specify a [specific block of time](..//nats-tools/nsc/nsc.md#user-authorization) during the day when applications can connect. For example, permit certain users or applications to access the system during specified business hours, or protect business operations during the busiest parts of the day from batch driven back-office applications that could adversely impact the system when run at the wrong time. ### Default User Permissions -Now you can specify [default user permissions](https://github.com/nats-io/nats.docs/tree/4009a69741789af8606c9fd475f92f2bed40ede3/TODO%20Link/README.md) within an account. This significantly reduces efforts around policy, reduces chances for error in permissioning, and simplifies the provisioning of user credentials. +Now you can specify [default user permissions](..//nats-server/configuration/securing_nats/authorization.md#examples) within an account. This significantly reduces efforts around policy, reduces chances for error in permissioning, and simplifies the provisioning of user credentials. ## WebSockets