Snowflake - Network Policy with Stitch best practice?

I know that Snowflake requires a network policy for Stitch to access a database. I also know that I have to add my own IP address to that network policy to access the data. What's the best way to manage this going forward? I'm thinking of events like my IP address changing or adding new users. Here are the options I can think of:

1. Just keep adding and updating IP addresses on the network policy
2. Create a different network policy to apply for users that allows access from any IP address

Create one network policy for users who will be admins so that any changes required would need to be updated only to the specific sub-set and another one for users who will need to be added as they are on-boarded. It all would come down to manageability of one or more policies. Please note that only 1 network policy can be attached at the account level.