Folders & Tagging

Nected provides a powerful tagging system that allows you to organize, categorize, and manage entities across your workspace. Tags are flexible labels that can be applied to rules, workflows, data sources, and other entities to create logical groupings, improve discoverability, and enable granular access control.

Tags in Nected follow a type-based structure, where each tag belongs to a specific category (tag type) and has a unique name within that category. This hierarchical approach enables you to create meaningful taxonomies that align with your organization's structure and workflows.

Key Benefits

Benefit	Description
Organization	Group related entities together for easier management and navigation
Discoverability	Quickly find entities using tag-based filtering and search
Access Control	Grant or restrict user access based on tags using Role-Based Access Control (RBAC)
Reporting	Create custom reports and dashboards based on tagged entity groups
Collaboration	Enable teams to work with specific subsets of entities based on their responsibilities
Scalability	Maintain organization as your workspace grows with hundreds of entities

Supported Entities

Tags can be applied to the following entities in your Nected workspace:

Entity Type	Description
Rules	Decision tables, simple rules, and rulesets that define your business logic
Workflows	Automated workflows that orchestrate multiple rules and actions
Data Sources	Database connections, API integrations, and other data connectors

Tags are workspace-scoped, meaning they are available across all branches within your workspace.

Tag Structure

Each tag in Nected consists of two components:

1. Tag Type (Category)

The tag type defines the category or classification system for the tag. Nected provides several predefined tag types to help you get started:

Predefined Tag Type	Use Case
Product Line	Organize entities by product or service offering
Region	Categorize by geographical location or market
Teams	Group entities by department or team ownership
Features	Classify by feature area or functionality
Environment	Distinguish between dev, staging, production entities
Priority	Mark entities by importance or urgency level

Custom Tag Types: You can create your own tag types by simply typing a new type name when creating a tag. This allows you to define custom taxonomies that match your organization's unique needs.

2. Tag Name

The tag name is the specific label within a tag type. For example:

• Tag Type: Region → Tag Name: North America, Europe, Asia-Pacific

• Tag Type: Teams → Tag Name: Engineering, Finance, Marketing

• Tag Type: Product Line → Tag Name: Core Banking, Insurance, Lending

3. Tag Color

Each tag can be assigned a color for visual identification. Colors help you quickly distinguish between different tags when viewing entities, making it easier to scan and identify relevant items at a glance.

How to Create Tags?

Tags in Nected are created through the Manage Tags page. You can access this interface when adding a tag to any entity.

Step-by-Step: Creating a New Tag

1. Navigate to an Entity

   • Go to the entity you want to tag (e.g., Rules page in the left sidebar)

   • Click on the specific entity to open its detail page

2. Open Tag Management

   • Look for the "+" button or tag icon near the entity title or in the entity details panel

   • Click the "+" button to open the tag modal

3. Access Manage Tags Page

   • In the tag modal, click "Manage Tags" or navigate to create a new tag

   • This opens the tag management interface

4. Create a New Tag

   • Click the "Create New Tag" button

   • A creation form will appear with the following fields:

   Field	Description	Required
   Tag Name	The specific label for your tag	Yes
   Tag Type	Select from predefined types or enter a custom type	Yes
   Color	Choose a color for visual identification	Yes

5. Select Tag Type

   • Choose from the predefined tag types dropdown:

     • Product Line

     • Region

     • Teams

     • Features

     • (and more...)

   • Or type a custom "tag type" to create a new category

6. Choose a Color

   • Select a color from the color picker

   • Colors help visually distinguish tags across the interface

7. Save the Tag

   • Click "Create" to save your new tag

   • The tag is now available to be applied to any supported entity

How to Apply Tags to Entities?

Once tags are created, you can apply them to any supported entity in your workspace.

Adding Tags to an Entity

1. Navigate to the Entity

   • Open the entity detail page (rule, workflow, or data source)

2. Open Tag Selector

   • Click the "+" button next to existing tags or in the tag section

3. Select Tags

   • A modal will display all available tags in your workspace

   • Tags are organized by their tag type for easy navigation

   • Click on one or more tags to select them

4. Apply Tags

   • Selected tags are immediately applied to the entity

   • Tags appear as colored badges on the entity

Viewing Applied Tags

• Tags appear as colored badges on entity cards in list views

• Tags are visible in entity detail pages

• Multiple tags can be applied to a single entity

Managing Tags

Editing Tags

To modify an existing tag:

1. Navigate to the Manage Tags page (accessible via the "+" button on any entity)

2. Find the tag you want to edit

3. Click the Edit icon or option next to the tag

4. Update the tag name, type, or color as needed

5. Save your changes

Note: Editing a tag affects all entities that have that tag applied. Changes are reflected immediately across your workspace.

Removing Tags from Entities

To remove a tag from a specific entity:

1. Open the entity detail page

2. Locate the tag you want to remove

3. Click the "×" icon on the tag badge, or

4. Open the tag selector and deselect the tag

Deleting Tags

To permanently delete a tag from your workspace:

1. Navigate to the Manage Tags page

2. Find the tag you want to delete

3. Click the Delete icon or option

4. Confirm the deletion

Warning: Deleting a tag removes it from all entities where it was applied. This action cannot be undone.

Tag-Based Access Control (RBAC)

One of the most powerful features of Nected's tagging system is its integration with Role-Based Access Control (RBAC). Tags can be used to define granular permissions, allowing you to control which users or teams can access specific entities.

How Tag-Based RBAC Works?

1. Create Tags that represent access boundaries (e.g., Teams: Engineering, Region: Europe)

2. Apply Tags to entities that should have restricted access

3. Configure User Roles to include or exclude specific tags:

   • Users can be granted access to entities with specific tags

   • Users can be restricted from accessing entities with certain tags

4. Automatic Filtering: When users navigate the workspace, they only see entities that match their tag-based permissions

Use Cases for Tag-Based Access Control

Scenario	Implementation
Team Isolation	Tag entities with team names; grant each team access only to their tagged entities
Regional Compliance	Tag entities by region; restrict access based on user's regional assignment
Environment Separation	Tag entities with Production, Staging, Development; limit production access to authorized users
Feature-Based Access	Tag entities by feature area; allow specialists to access only their domain

Example: Team-Based Access

Tags Created:
- Teams: Engineering
- Teams: Finance
- Teams: Marketing

User Configuration:
- Engineering team members → Access to "Teams: Engineering" tagged entities
- Finance team members → Access to "Teams: Finance" tagged entities
- Admin users → Access to all tags

---

Filtering and Searching by Tags

Tags enhance the discoverability of entities across your workspace through powerful filtering capabilities.

Filtering Entities by Tag

1. Navigate to Entity List

   • Go to the Rules, Workflows, or Data Sources page

2. Open Filter Options

   • Look for the Filter or Tags dropdown in the list toolbar

3. Select Tags to Filter

   • Choose one or more tags from the dropdown

   • The list updates to show only entities matching the selected tags

4. Combine Filters

   • Tags can be combined with other filters (name, type, status)

   • Multiple tag selections can use AND/OR logic depending on configuration

Search Integration

• Tags are included in search results

• Searching for a tag name will return all entities with that tag

• Tags appear in search result previews for quick identification

---

Best Practices

Naming Conventions

Practice	Description	Example
Be Descriptive	Use clear, meaningful names	Credit Risk Assessment instead of CRA
Stay Consistent	Use consistent naming patterns across tags	Always use Region: [Name] format
Avoid Redundancy	Don't duplicate information already in entity names	Tag with Product: Lending, not Lending Rule
Use Hierarchies	Leverage tag types for logical grouping	Product Line > Feature > Component

Tag Type Strategy

1. Start Simple: Begin with 3-5 core tag types that address your most pressing organizational needs

2. Expand Gradually: Add new tag types as your use cases evolve

3. Review Periodically: Audit your tags quarterly to remove unused ones and consolidate duplicates

Color Coding Guidelines

Color Usage	Recommendation
Red	Critical, high-priority, or production entities
Green	Approved, active, or healthy status
Blue	Standard, informational tags
Yellow/Orange	Attention needed, pending review
Purple	Special categories or experimental features
Gray	Deprecated or archived entities

Performance Considerations

• Apply only necessary tags to keep entity metadata clean

• Use tag types to organize rather than creating flat lists of tags

• Periodically clean up unused or orphaned tags

---

Common Use Cases

1. Multi-Team Workspace Management

Scenario: Your workspace contains rules and workflows created by multiple teams.

Solution:

• Create Teams tag type with values: Engineering, Data Science, Operations

• Tag all entities with their owning team

• Configure RBAC to give each team access to their tagged entities

• Leadership can access all tags for cross-team visibility

2. Product Line Organization

Scenario: You have rules for different product lines that need separation.

Solution:

• Create Product Line tag type: Banking, Insurance, Investments

• Create Feature tag type: Onboarding, Risk Assessment, Compliance

• Combine tags for precise categorization: Product Line: Banking + Feature: Risk Assessment

3. Environment-Based Access Control

Scenario: You need to restrict production rule access to senior engineers.

Solution:

• Create Environment tag type: Development, Staging, Production

• Tag rules based on their deployment environment

• Grant Production tag access only to authorized personnel

4. Regional Compliance

Scenario: Different regions have different regulatory requirements.

Solution:

• Create Region tag type: US, EU, APAC

• Tag compliance rules by applicable region

• Use RBAC to ensure regional teams see only relevant rules

5. Project-Based Organization

Scenario: You're working on multiple projects with overlapping rules.

Solution:

• Create Project tag type with active project names

• Tag entities by their associated project

• Filter views by project for focused work sessions

Troubleshooting

Common Issues

Issue	Cause	Solution
Tag not appearing	Tag may not be saved properly	Refresh the page; re-create the tag if missing
Cannot delete tag	Tag may be in use by entities	Remove tag from all entities first, then delete
Access denied to tagged entity	RBAC restrictions	Check user role permissions for the applied tags
Duplicate tags	Multiple tags with similar names	Consolidate tags and update entity assignments
Tag color not visible	Display rendering issue	Try a different browser or clear cache

FAQs

Q: Can I apply multiple tags of the same type to an entity? A: Yes, you can apply multiple tags from the same tag type. For example, an entity can have both Region: US and Region: EU tags.

Q: Are tags case-sensitive? A: Tag names are generally case-insensitive for matching purposes, but the display preserves your original capitalization.

Q: Can I rename a tag type? A: Currently, tag types cannot be renamed directly. You would need to create a new tag type and migrate your tags.

Q: How many tags can I apply to a single entity? A: There is no strict limit, but we recommend keeping tags focused and relevant (typically 3-7 tags per entity).

Q: Do tags sync across branches? A: Tags are workspace-scoped and available across all branches within your workspace.

Related Documentation

• Role-Based Access Control (RBAC): Learn how to configure user roles and permissions

• Rules Documentation: Detailed guide on creating and managing rules

• Workflows Documentation: Learn about workflow creation and management

• Datasets: Guide to connecting and managing datasets