Reference documentation and code samples for the Identity Access Context Manager v1 API enum ServicePerimeter.Types.PerimeterType.
Specifies the type of the Perimeter. There are two types: regular and
bridge. Regular Service Perimeter contains resources, access levels, and
restricted services. Every resource can be in at most ONE
regular Service Perimeter.
In addition to being in a regular service perimeter, a resource can also
be in zero or more perimeter bridges. A perimeter bridge only contains
resources. Cross project operations are permitted if all effected
resources share some perimeter (whether bridge or regular). Perimeter
Bridge does not contain access levels or services: those are governed
entirely by the regular perimeter that resource is in.
Perimeter Bridges are typically useful when building more complex toplogies
with many independent perimeters that need to share some data with a common
perimeter, but should not be able to share data among themselves.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThe latest version available for the \u003ccode\u003eServicePerimeter.Types.PerimeterType\u003c/code\u003e is 2.5.0, with several older versions also accessible.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eServicePerimeter.Types.PerimeterType\u003c/code\u003e is an enum within the Identity Access Context Manager v1 API, found in the \u003ccode\u003eGoogle.Identity.AccessContextManager.V1\u003c/code\u003e namespace.\u003c/p\u003e\n"],["\u003cp\u003eThe enum \u003ccode\u003eServicePerimeter.Types.PerimeterType\u003c/code\u003e defines two types of service perimeters: \u003ccode\u003eRegular\u003c/code\u003e and \u003ccode\u003eBridge\u003c/code\u003e, each serving distinct roles in resource management and access control.\u003c/p\u003e\n"],["\u003cp\u003eRegular perimeters contain resources, access levels, and restricted services, while bridge perimeters only contain resources and are used for sharing data among multiple independent perimeters.\u003c/p\u003e\n"],["\u003cp\u003eCross-project operations are allowed between resources if they share at least one service perimeter, whether it is a regular or bridge type.\u003c/p\u003e\n"]]],[],null,["# Identity Access Context Manager v1 API - Enum ServicePerimeter.Types.PerimeterType (2.5.0)\n\nVersion latestkeyboard_arrow_down\n\n- [2.5.0 (latest)](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/latest/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [2.4.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/2.4.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [2.3.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/2.3.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [2.2.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/2.2.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [2.1.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/2.1.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [2.0.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/2.0.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [1.5.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/1.5.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [1.4.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/1.4.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [1.3.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/1.3.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType)\n- [1.2.0](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/1.2.0/Google.Identity.AccessContextManager.V1.ServicePerimeter.Types.PerimeterType) \n\n public enum ServicePerimeter.Types.PerimeterType\n\nReference documentation and code samples for the Identity Access Context Manager v1 API enum ServicePerimeter.Types.PerimeterType.\n\nSpecifies the type of the Perimeter. There are two types: regular and\nbridge. Regular Service Perimeter contains resources, access levels, and\nrestricted services. Every resource can be in at most ONE\nregular Service Perimeter.\n\nIn addition to being in a regular service perimeter, a resource can also\nbe in zero or more perimeter bridges. A perimeter bridge only contains\nresources. Cross project operations are permitted if all effected\nresources share some perimeter (whether bridge or regular). Perimeter\nBridge does not contain access levels or services: those are governed\nentirely by the regular perimeter that resource is in.\n\nPerimeter Bridges are typically useful when building more complex toplogies\nwith many independent perimeters that need to share some data with a common\nperimeter, but should not be able to share data among themselves.\n\nNamespace\n---------\n\n[Google.Identity.AccessContextManager.V1](/dotnet/docs/reference/Google.Identity.AccessContextManager.V1/latest/Google.Identity.AccessContextManager.V1)\n\nAssembly\n--------\n\nGoogle.Identity.AccessContextManager.V1.dll"]]