<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[BoldSign - Medium]]></title>
        <description><![CDATA[An enterprise-grade electronic signature application and API with all the bells and whistles at an affordable price. Easily collect legally binding eSignatures online from our app or yours. - Medium]]></description>
        <link>https://medium.com/boldsign?source=rss----2834968ad290---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>BoldSign - Medium</title>
            <link>https://medium.com/boldsign?source=rss----2834968ad290---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:14:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/boldsign" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[EF Core vs. Dapper: Which .NET Data Access Tool Should You Use]]></title>
            <link>https://medium.com/boldsign/ef-core-vs-dapper-fbf29aa49df3?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/fbf29aa49df3</guid>
            <category><![CDATA[orm-for-dotnet]]></category>
            <category><![CDATA[raw-sql-vs-orm]]></category>
            <category><![CDATA[entity-framework-core]]></category>
            <category><![CDATA[dapper-vs-ef-core]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Wed, 15 Apr 2026 11:02:17 GMT</pubDate>
            <atom:updated>2026-08-11T17:23:11.792Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="EF Core vs. Dapper: Which .NET Data Access Tool Should You Use" src="https://cdn-images-1.medium.com/max/768/1*pAzwq3vQNCrlHTi7rClWgg.png" /></figure><p><strong>TL;DR</strong>: This guide compares EF Core vs. Dapper in terms of abstraction, performance, and SQL control, explaining when each fits best and why many .NET teams combine both in real-world applications.</p><h3>EF Core vs. Dapper: What should you use</h3><p>Use EF Core when you want a full ORM that boosts productivity and long-term maintainability (LINQ, change tracking, migrations, cross-database providers). Use Dapper when you want maximum SQL control and minimal overhead, especially for read-heavy or performance-critical endpoints. If you’re building a large system, a hybrid approach (using EF Core for writes and Dapper for reads) often provides the best balance.</p><h3>How do you choose between EF Core and Dapper in 60 seconds</h3><p>Choose EF Core if most of these are true:</p><ul><li>You’re building CRUD-heavy business features.</li><li>You want LINQ and strongly typed query composition.</li><li>You benefit from change tracking and unit-of-work patterns.</li><li>You want migrations and schema evolution built in (<a href="https://learn.microsoft.com/en-us/ef/core/managing-schemas/migrations/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>).</li><li>You want easy provider switching across databases (<a href="https://learn.microsoft.com/en-us/ef/core/providers/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>).</li></ul><p>Choose Dapper if most of these are true:</p><ul><li>You need handwritten SQL for complex joins, common table expressions (CTEs), or reporting.</li><li>You’re optimizing a hot path where overhead matters.</li><li>Your queries return data transfer objects (DTOs) or projections, not domain aggregates.</li><li>You want SQL that’s transparent to debug and tune.</li></ul><p>Choose hybrid (EF Core and Dapper) if:</p><ul><li>Writes benefit from EF Core’s tracking and transactions.</li><li>Reads need fast projections and SQL control (dashboards, search, reporting).</li><li>You’re already doing command query responsibility segregation (CQRS)-style separation, even informally.</li></ul><h3>What is EF Core and why does it exist</h3><p>Entity Framework Core (EF Core) is Microsoft’s modern, cross-platform, open-source ORM for .NET that lets you work with a database using .NET objects and reduces repetitive data-access code. (<a href="https://learn.microsoft.com/en-us/ef/core/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>At its core, EF Core exists to help developers program against a conceptual model instead of writing and maintaining large amounts of database plumbing manually — a goal that historically shaped Entity Framework as a concept. (<a href="https://learn.microsoft.com/en-us/dotnet/framework/data/adonet/ado-net-technology-options-and-guidelines/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><h3>What is Dapper and why does it exist</h3><p>Dapper is a simple object mapper for .NET that focuses on executing SQL and efficiently mapping results to objects with minimal abstraction. (<a href="https://github.com/DapperLib/Dapper/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">GitHub</a>)<br>It exists to keep data access fast, explicit, and SQL-first, especially when teams want to avoid the overhead and “magic” of a full ORM.</p><h3>What does ORM vs. micro ORM mean in practice</h3><p>An ORM like EF Core typically provides:</p><ul><li>Query composition (LINQ).</li><li>Relationship handling.</li><li>Change tracking and unit-of-work behavior. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>Migrations and schema management. (<a href="https://learn.microsoft.com/en-us/ef/core/managing-schemas/migrations/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>A provider model across databases. (<a href="https://learn.microsoft.com/en-us/ef/core/providers/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li></ul><p>A micro ORM like Dapper typically provides:</p><ul><li>SQL execution helpers.</li><li>Fast mapping from rows to objects.</li><li>Minimal overhead and minimal “model management.”</li></ul><p>Mental model of EF Core vs. Dapper</p><ul><li>EF Core is a full-service kitchen: you place an order (LINQ/model), it cooks (SQL translation), serves (materialization), and cleans up (tracking).</li><li>Dapper is your own kitchen: you cook the SQL yourself, and Dapper helps plate it efficiently.</li></ul><h3>How does EF Core map data and track changes</h3><p>EF Core is centered around a DbContext, which represents a session with the database and enables querying and saving. (<a href="https://learn.microsoft.com/en-us/ef/core/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>When queries return entity types, EF Core tracks entities by default, keeping state in a change tracker so modifications can be persisted on SaveChanges. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><h4>Simplified procedure (text diagram):</h4><figure><img alt="EF Core query execution flow" src="https://cdn-images-1.medium.com/max/914/1*Wainoycpzq660q5MZM9noQ.png" /><figcaption>EF Core query execution flow</figcaption></figure><p>EF Core explicitly passes a representation of the LINQ query to the provider, and the provider translates it to the database-specific language, such as SQL. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><h3>How does Dapper map query results to objects</h3><p>Dapper is intentionally thin and performs very little work beyond executing SQL and mapping result rows to objects. This makes its runtime behavior predictable and its performance characteristics easy to diagnose under load. It works like this:</p><ul><li>You write the SQL.</li><li>Dapper executes it using ADO.NET.</li><li>Each result row is mapped directly to an object or DTO by matching column names to properties.</li></ul><p>There is no change tracking, relationship fix-up, or schema model. As stated on its GitHub page, Dapper’s focus is being a “simple object mapper.”</p><h3>What EF Core features matter most in real systems</h3><p>These are the features that usually drive teams toward EF Core for core business logic.</p><h4>How do DbContext and DbSet shape your architecture</h4><p><em>A quick explanation of how EF Core “wants” you to structure data access.</em></p><p>EF Core uses a model made up of entity classes and a context object (DbContext) representing a database session. (<a href="https://learn.microsoft.com/en-us/ef/core/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>This naturally fits:</p><ul><li>Unit-of-work patterns.</li><li>Aggregate-centric domain modeling.</li><li>Transactional write workflows.</li></ul><h4>Why do migrations change how teams manage schema</h4><p><em>Migrations are a workflow decision as much as a feature.</em></p><p>EF Core migrations are source-controlled changes generated by comparing the current model to a previous snapshot, and EF Core records applied migrations in a history table. (<a href="https://learn.microsoft.com/en-us/ef/core/managing-schemas/migrations/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>This makes schema evolution part of normal development, not a separate manual process.</p><h4>How do lazy loading and eager loading affect performance</h4><p><em>Loading strategy is one of the most common sources of “EF is slow” incidents.</em></p><p>EF Core supports lazy loading via proxies, but it can cause extra database roundtrips (the classic N+1 problem). (<a href="https://learn.microsoft.com/en-us/ef/core/querying/related-data/lazy/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>That’s why many production teams prefer explicit eager loading for predictable query shapes.</p><h3>What Dapper features matter most in real systems</h3><p>These are the features that usually drive teams toward Dapper for read paths and reporting.</p><h4>Why does SQL-first data access improve debugging and tuning</h4><p><em>When the query is the product, SQL-first often wins.</em></p><p>Because you own the SQL, you can:</p><ul><li>Copy and paste queries into your DB console.</li><li>Tune indexes and query plans directly.</li><li>Use database-specific features (CTEs, window functions, and hints where appropriate).</li></ul><h4>Why does no change tracking change your write strategy</h4><p><em>This is where micro ORM simplicity can become a cost.</em></p><p>Dapper doesn’t track entity state, so writes are explicit:</p><ul><li>You decide when to INSERT and UPDATE.</li><li>You manage concurrency patterns (row version/time stamps, etc.)</li><li>You build your own unit-of-work behavior (if needed).</li></ul><h3>EF Core vs. Dapper: Feature comparison table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*Ry4FLQEQSvdbGods6llMDA.png" /></figure><h3>Where performance differences really come from</h3><p><em>This section explains performance in terms of framework overhead, query shape, and database behavior.</em></p><h4>When does EF Core overhead matter</h4><p>EF Core can be fast, but features have costs.</p><p>EF Core tracking keeps entity instances in the change tracker, and no-tracking queries are generally quicker in read-only scenarios because there’s no need to set up tracking info. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>EF Core overhead tends to show up when:</p><ul><li>You load lots of entities into memory.</li><li>You do high-frequency read paths with tracking on.</li><li>You rely on lazy loading and trigger many roundtrips. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/related-data/lazy/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li></ul><h4>When does Dapper win (and when is it irrelevant)</h4><p>Dapper’s gains are biggest when your app is CPU- or alloc-heavy, not DB-bound.</p><p>Dapper often shines when:</p><ul><li>You return lightweight DTO projections.</li><li>You run many short queries per second.</li><li>You avoid extra allocations and tracking.</li></ul><p>But if your bottleneck is:</p><ul><li>network latency</li><li>slow queries or missing indexes</li><li>lock contention</li></ul><p>…then switching ORMs won’t save you.</p><h3>Code: Simple SELECT with EF Core vs. Dapper</h3><p>Side-by-side examples make the difference in abstraction level obvious.</p><h4>EF Core (LINQ and optional no-tracking)</h4><p><strong>c#</strong></p><pre><br>// Entities: User { Id, FirstName, LastName, IsActive }<br>var users = await db.Users<br>    .AsNoTracking() // best default for read-only lists<br>    .Where(u =&gt; u.IsActive)<br>    .OrderBy(u =&gt; u.LastName)<br>    .Select(u =&gt; new { u.Id, u.FirstName, u.LastName }) //projection helps performance<br>    .ToListAsync();</pre><p>EF Core’s tracking versus no-tracking behavior is an explicit lever, and no-tracking is typically preferred for read-only queries. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><h4>Dapper (SQL and parameters)</h4><p><strong>c#</strong></p><pre><br>const string sql = &quot;&quot;&quot;<br>SELECT Id, FirstName, LastName<br>FROM Users<br>WHERE IsActive = @IsActive<br>ORDER BY LastName;<br>&quot;&quot;&quot;;<br>var users = await connection.QueryAsync(<br>    sql,<br>    new { IsActive = true }<br>);<br>public sealed record UserListItem(int Id, string FirstName, string LastName);</pre><h3>Code: Insert/update with EF Core vs. Dapper</h3><p>Writes are where EF Core’s unit-of-work model changes day-to-day productivity.</p><h4>EF Core (Tracked entity + SaveChanges)</h4><p><strong>c#</strong></p><pre><br>db.Users.Add(new User<br>{<br>    FirstName = &quot;John&quot;,<br>    LastName = &quot;V&quot;,<br>    IsActive = true<br>});<br>await db.SaveChangesAsync();</pre><h4>Dapper (explicit SQL)</h4><p><strong>c#</strong></p><pre><br>const string insertSql = &quot;&quot;&quot;<br>INSERT INTO Users (FirstName, LastName, IsActive)<br>VALUES (@FirstName, @LastName, @IsActive);<br>&quot;&quot;&quot;;<br>await connection.ExecuteAsync(insertSql, new <br>{ <br>    FirstName = &quot;John&quot;,<br>    LastName = &quot;V&quot;,<br>    IsActive = true<br>});</pre><h3>Code: Performance-focused query patterns you can actually use</h3><p><em>Practical techniques that help more than “switch ORM” does.</em></p><h4>How do you speed up hot EF Core read paths with compiled queries</h4><p>Compiled queries can reduce repeated translation overhead on frequently executed queries.</p><p>EF Core provides EF.CompileQuery to create a compiled query delegate. (<a href="https://learn.microsoft.com/en-us/dotnet/api/microsoft.entityframeworkcore.ef.compilequery?view=efcore-10.0&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p><strong>c#</strong></p><pre><br>private static readonly Func&gt; ActiveUsersQuery =<br>    EF.CompileAsyncQuery((AppDbContext db, bool isActive) =&gt;<br>        db.Users<br>          .AsNoTracking()<br>          .Where(u =&gt; u.IsActive == isActive)<br>          .OrderBy(u =&gt; u.LastName)<br>          .Select(u =&gt; new UserListItem(u.Id, u.FirstName, u.LastName)));<br>public async Task&gt; GetActiveUsersAsync(bool isActive, CancellationToken ct) <br>{<br>    var result = new List();<br>    await foreach (var item in ActiveUsersQuery(db, isActive).WithCancellation(ct))<br>        result.Add(item);<br>    return result;<br>}</pre><h4>How do you keep Dapper fast and safe for hot endpoints</h4><p>The “easy win” is correct parameterization and tight projections.</p><p><strong>c#</strong></p><pre><br>const string sql = &quot;&quot;&quot;<br>SELECT Id, FirstName, LastName<br>FROM Users<br>WHERE IsActive = @IsActive AND LastName &gt;= @Start<br>ORDER BY LastName<br>OFFSET @Skip ROWS FETCH NEXT @Take ROWS ONLY;<br>&quot;&quot;&quot;;<br>var page = await connection.QueryAsync(sql, new<br>{<br>    IsActive = true,<br>    Start = &quot;M&quot;,<br>    Skip = 0,<br>    Take = 50<br>});</pre><h3>Which tool fits common .NET application types</h3><p>The following table is a scenario-based mapping that developers and architects can use during design review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*T7ach7TBWBK1rL1erNul3g.png" /></figure><h3>When does a hybrid EF Core + Dapper approach make sense</h3><p>A hybrid EF Core–Dapper approach is commonly used in larger systems that need strong transactional guarantees for writes and high-performance, predictable reads.</p><p>This approach is inspired by the core idea of Command Query Responsibility Segregation (CQRS), which separates data-modifying operations (commands) from data-retrieval operations (queries). However, it does not implement full CQRS. Instead, it applies the principle in a pragmatic way, without introducing additional architectural complexity, such as command/query handler pipelines, message buses, separate read/write models, or event sourcing.</p><p>A hybrid approach is usually justified when:</p><ul><li>The write model benefits from EF Core, including change tracking, relationship management, and transactional workflows. (<a href="https://learn.microsoft.com/en-us/ef/core/change-tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>The read model benefits from explicit SQL, optimized projections, and high-throughput query execution.</li><li>Schema evolution is managed through EF Core migrations, keeping database changes centralized. (<a href="https://learn.microsoft.com/en-us/ef/core/managing-schemas/migrations/?tabs=dotnet-core-cli&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li></ul><h4>Simplified data access flow (CQRS-inspired)</h4><figure><img alt="Simplified CQRS-style data access flow using EF Core and Dapper" src="https://cdn-images-1.medium.com/max/1024/1*B6kaeS7jVjberRwzmFfpvQ.png" /><figcaption>Simplified CQRS-style data access flow using EF Core and Dapper</figcaption></figure><p>What this diagram shows:</p><ul><li>EF Core is used for database writes, where tracking and transactions are valuable.</li><li>Dapper is used for database reads, where explicit SQL and minimal overhead provide better performance.</li><li>Both reads and writes operate against the same database.</li><li>This separation reflects CQRS principles without the full CQRS infrastructure.</li></ul><h3>How to implement EF Core for writes and Dapper for reads in an ASP.NET Core app</h3><p><em>Straightforward setup with safe connection/transaction handling patterns.</em></p><h4>Step 1: Keep EF Core as your primary unit of work</h4><p>Use DbContext for write workflows and schema management:</p><ul><li>Keep writes in an application service or command handler.</li><li>Use migrations for schema changes. (<a href="https://learn.microsoft.com/en-us/ef/core/managing-schemas/migrations/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li></ul><h4>Step 2: Add a query service that uses Dapper for projections</h4><p>Make reads explicit, DTO-oriented, and easy to tune.</p><p><strong>c#</strong></p><pre><br>public sealed class UserReadService<br>{<br>    private readonly AppDbContext _db;<br>    public UserReadService(AppDbContext db) =&gt; _db = db;<br>    public async Task&gt; SearchUsersAsync(string term, CancellationToken ct)<br>    {<br>        var conn = _db.Database.GetDbConnection();<br>        const string sql = &quot;&quot;&quot;<br>        SELECT TOP (50) Id, FirstName, LastName<br>        FROM Users<br>        WHERE LastName LIKE @Term OR FirstName LIKE @Term<br>        ORDER BY LastName;<br>        &quot;&quot;&quot;;<br>        // Ensure connection is open (EF opens it for its own operations; be explicit here)<br>        if (conn.State != System.Data.ConnectionState.Open)<br>            await conn.OpenAsync(ct);<br>        var rows = await conn.QueryAsync(sql, new { Term = $&quot;%{term}%&quot; });<br>        return rows.AsList();<br>    }<br>}</pre><h4>Step 3: Share a transaction when you truly need read-your-writes</h4><p><em>Only do this when required; otherwise keep reads and writes separate for simplicity.</em></p><p>In EF Core, you can start a transaction via DbContext.Database. Then you can pass the underlying DbTransaction to Dapper so that both participate in the same transaction boundary.</p><p><strong>Note</strong>: Exact APIs vary slightly across EF Core versions and providers; if your team has a standard pattern, align with it. If uncertain, this needs to be clarified by the engineering team.</p><h3>Best practices for EF Core and Dapper in production</h3><p>Operational habits that prevent 80% of incidents.</p><h4>How do you keep EF Core predictable under load</h4><p>Treat EF Core as a powerful tool that needs guardrails.</p><ul><li>Prefer projections (SELECT) for read endpoints instead of returning full entities.</li><li>Use no-tracking for read-only queries. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>Avoid accidental lazy loading in request paths (N+1 risk). (<a href="https://learn.microsoft.com/en-us/ef/core/querying/related-data/lazy/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>Log SQL, timings, and parameter values with appropriate redaction.</li></ul><h4>How do you keep Dapper safe and maintainable</h4><p>Most Dapper problems are not performance — they’re governance.</p><ul><li>Always parameterize (never string-concatenate user input).</li><li>Store SQL in named queries (constants/files) with code review.</li><li>Prefer explicit column lists (avoid SELECT *).</li><li>Write integration tests for complex queries (schema drift happens).</li></ul><h4>What should you monitor regardless of ORM choice</h4><p>Observability beats ideology.</p><ul><li>Query duration percentiles (P50/P95/P99)</li><li>DB CPU, locks, deadlocks, and slow query logs</li><li>Connection pool saturation</li><li>Error rates and timeouts at the API layer</li></ul><h3>Common mistakes developers make with EF Core and Dapper</h3><p>These are predictable failure modes you can prevent with code review:</p><ul><li>Using EF Core tracking for read endpoints by default: Tracking has purpose, but read-only queries are generally faster than no-tracking. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>Allowing lazy loading in high-traffic code paths: Lazy loading can cause extra round trips (N+1). (<a href="https://learn.microsoft.com/en-us/ef/core/querying/related-data/lazy/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>Blaming the ORM for slow queries without checking the DB plan: Missing indexes and bad query shapes dominate most performance issues.</li><li>Overusing Dapper for complex write workflows: You’ll rebuild unit of work, concurrency handling, and relationship integrity manually.</li><li>Letting SQL sprawl: Without conventions, Dapper codebases can become string soup.</li></ul><h3>Summary: EF Core vs. Dapper</h3><ul><li>EF Core is a full ORM that improves productivity with LINQ, tracking, migrations, and providers. (<a href="https://learn.microsoft.com/en-us/ef/core/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>Dapper is a simple object mapper that keeps SQL explicit and overhead low. (<a href="https://github.com/DapperLib/Dapper/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">GitHub</a>)</li><li>Performance differences matter most on hot read paths, large result sets, or when tracking or lazy loading is misused. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</li><li>A hybrid approach is often the most practical option in real systems.</li></ul><h3>FAQs</h3><p><strong>Is Dapper always faster than EF Core?</strong></p><p>Dapper often has lower overhead for reads because it doesn’t do tracking or LINQ translation, but real-world performance depends heavily on query shape, indexes, and database latency.</p><p><strong>Can EF Core run raw SQL when needed?</strong></p><p>Yes. EF Core supports raw SQL patterns (useful for edge cases), but Dapper is typically more natural for SQL-first query services.</p><p><strong>Should I use EF Core tracking by default?</strong></p><p>For entities you plan to modify and save, tracking is useful. For read-only endpoints, no tracking is generally quicker. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/tracking/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p><strong>Is lazy loading a good idea in EF Core?</strong></p><p>It can be convenient, but it can also cause extra round trips (N+1). Many teams disable it in request-heavy services. (<a href="https://learn.microsoft.com/en-us/ef/core/querying/related-data/lazy/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p><strong>Can I use EF Core migrations even if I use Dapper for queries?</strong></p><p>Yes. Migrations are independent of how you query. EF Core compares model snapshots, generates migration files, and tracks applied migrations in a history table. (<a href="https://learn.microsoft.com/en-us/ef/core/managing-schemas/migrations/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p><strong>What’s the safest way to keep Dapper queries secure?</strong></p><p>Always parameterize SQL, avoid string concatenation, and validate user inputs. Use least-privilege DB accounts and restrict dangerous permissions.</p><p><strong>When should I migrate from EF Core to Dapper?</strong></p><p>Only when profiling shows EF Core overhead is a meaningful bottleneck, and the cost of managing SQL manually is justified.</p><p><strong>Can EF Core really support multiple databases?</strong></p><p>Yes. EF Core uses database providers distributed as NuGet packages and supports many engines via its provider model. (<a href="https://learn.microsoft.com/en-us/ef/core/providers/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Microsoft Learn</a>)</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on January 29, 2026</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbf29aa49df3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/ef-core-vs-dapper-fbf29aa49df3">EF Core vs. Dapper: Which .NET Data Access Tool Should You Use</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How BoldSign Users Can Stay Safe Online from Fraud and Email Scams]]></title>
            <link>https://medium.com/boldsign/how-to-stay-safe-online-fraud-email-scams-cb2e742cadd3?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/cb2e742cadd3</guid>
            <category><![CDATA[online-form]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[electronic-signatures]]></category>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[email-scam]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Wed, 15 Apr 2026 11:02:05 GMT</pubDate>
            <atom:updated>2026-04-15T11:02:05.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How BoldSign Users Can Stay Safe Online from Fraud and Email Scams" src="https://cdn-images-1.medium.com/max/768/1*QHvkWVYqaDB6zR9QtvYvYA.png" /></figure><p>At BoldSign, safeguarding your data is our top priority. We’re constantly enhancing our platform’s security to protect you. However, in today’s digital landscape, online fraud and email scams are a growing challenge for everyone — not just BoldSign users. Scammers often impersonate trusted brands, including e-signature platforms, to trick people into sharing sensitive information.</p><p>One common tactic involves fraudsters creating accounts on legitimate services — like many platforms across industries — to send deceptive documents or emails. While BoldSign developers actively work to detect and prevent such misuse, staying vigilant is key to keeping yourself secure. In this post, we’ll equip you with practical tips to spot fraud, avoid scams, and report suspicious activity — ensuring you can use BoldSign with confidence.</p><h3>Identifying Fraud: Key Signs to Watch For</h3><ul><li><strong>Suspicious Email Addresses</strong>: Legitimate BoldSign emails always come from a @boldsign.com or @syncfusion.com domain. Be wary of misspelled or unfamiliar email addresses pretending to represent us.</li><li><strong>Vague Greetings</strong>: Scammers often use generic salutations like “Dear Customer” instead of your name. BoldSign communications are personalized — generic greetings are a red flag.</li><li><strong>Spelling, Grammar, or Formatting Errors</strong>: Fraudulent emails may contain typos, poor grammar, or inconsistent branding (e.g., a distorted logo). BoldSign emails are professionally crafted and reviewed — errors suggest a fake.</li><li><strong>Requests for Sensitive Information</strong>: BoldSign will never ask for personal or financial details via unsolicited emails or links. Treat such requests as suspicious.</li><li><strong>Pressure Tactics</strong>: Scammers may push you to act fast (e.g., “Your account will expire unless you click now”). BoldSign doesn’t use high-pressure tactics — take your time to verify.</li><li><strong>Suspicious Attachments</strong>: Avoid opening unexpected attachments. Always confirm the sender’s legitimacy first.</li><li><strong>Unsafe Websites</strong>: When entering personal information, ensure the URL starts with “https://” (the “s” indicates a secure site). If it’s missing, don’t proceed.</li><li><strong>Pop-Up Boxes</strong>: BoldSign never includes pop-ups in emails — they’re a security risk. If you see one, it’s not from us.</li></ul><h3>How to Avoid Fraud</h3><ul><li><strong>Verify Email Sources</strong>: Unsure about an email claiming to be from BoldSign? Contact our support team directly at <a href="/service/mailto:support@boldsign.com">support@boldsign.com</a> to confirm its authenticity.</li><li><strong>Secure Your Account</strong>: Use a strong password and enable two-factor authentication (2FA) in your BoldSign account for an extra layer of protection.</li><li><strong>Educate Your Team</strong>: Share these tips with colleagues or employees to ensure everyone in your organization can spot phishing attempts.</li><li><strong>Avoid Unknown Links and Attachments</strong>: Only interact with links or files you trust. When in doubt, verify with us first.</li></ul><h3>How to Report Fraud</h3><p>If you encounter a suspicious email, text, or fake BoldSign website, please forward it to <a href="/service/mailto:support@boldsign.com">support@boldsign.com</a>. Include details like the sender’s address, email content, and any links or attachments. Our team will investigate promptly and take action to protect our users.</p><p>Stay proactive and keep fraudsters at bay. We’re here to support you — reach out anytime if you need help or have concerns. With these tools and our commitment to security, you can sign and send documents with peace of mind.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on March 19, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb2e742cadd3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/how-to-stay-safe-online-fraud-email-scams-cb2e742cadd3">How BoldSign Users Can Stay Safe Online from Fraud and Email Scams</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BoldSign team at the SACS 2025 User Conference: Strengthening Partnerships]]></title>
            <link>https://medium.com/boldsign/sacs-2025-user-conference-a8cfd1b9974d?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/a8cfd1b9974d</guid>
            <category><![CDATA[digital-innovation]]></category>
            <category><![CDATA[sacs-2025]]></category>
            <category><![CDATA[digital-signing]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[sacs-software]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 11:11:40 GMT</pubDate>
            <atom:updated>2026-04-08T11:11:38.556Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="BoldSign team at the SACS 2025 User Conference : Strengthening Partnerships" src="https://cdn-images-1.medium.com/max/768/1*ZNrDlfsfepdkmSfOfqS-mQ.png" /></figure><p>The SACS 2025 User Conference at the Sandestin Golf and Beach Resort in Florida was the perfect setting to celebrate how our collaboration with SACS Software continues to grow. As a trusted provider of software and services for housing authorities, SACS Software is known for its commitment to innovation and customer care.</p><p>Building on that spirit of connection, SACS has embedded BoldSign directly into its application, giving clients a seamless way to send, sign, and manage documents without ever leaving the SACS platform. The integration makes it easier than ever for housing authorities to move toward efficient, paperless, and secure workflows, combining SACS’s deep industry expertise with BoldSign’s modern digital signing technology.</p><h3>A business family that loves what they do</h3><p>The SACS community is more than a group of clients — it’s a business family. Throughout the conference, one word kept surfacing: love. Attendees repeatedly expressed how much they love SACS Software and the people behind it. Many spoke about how the SACS team is always there to support them and their teams, a testament to the company’s dedication and customer-first culture.</p><h3>Sharing stories that inspire</h3><p>During the general session on day one, we were thrilled to share a video case study highlighting a real-world success story and the impact of our BoldSign signature solution within the SACS Software platform. Elizabeth Moncrief of the Western Piedmont Council of Government described how BoldSign saved time, enabled easy tracking and retrieval of signed documents, and brought her team closer to the goal of achieving paperless operations. She also talked about how one of their clients could remotely sign all of their paperwork during a 15-minute break, whereas an in-person visit would have really disrupted the client’s workday without the integration.</p><figure><img alt="Attendees watching the BoldSign and SACS Software video case study during the general session." src="https://cdn-images-1.medium.com/max/864/1*I_oXX1Ao5CvLnPIgadjCuA.png" /><figcaption><em>Attendees watching the BoldSign and SACS </em>S<em>oftware video case study during the general session.</em></figcaption></figure><h3>A wave of interest in BoldSign</h3><p>Following the general session, our booth was buzzing with interest in digital signing and BoldSign, our secure e-signature platform. It was inspiring to see how eager attendees were to explore how BoldSign can simplify document workflows and enhance productivity. BoldSign aligns perfectly with the industry’s goal of going paperless — a desire echoed by nearly every agency in attendance.</p><h3>Building connections over lunch</h3><p>We had the pleasure of attending the lunch on day one, where attendees enjoyed great food, lively conversations, and a few fun surprises — including BoldSign mugs and two $250 gift cards given away to lucky winners! The giveaways added a burst of excitement to an already engaging afternoon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3F1AMNBtb9MJPlvnDtt-uA.png" /><figcaption><em>Lunch on day one was filled with great conversations, BoldSign giveaways, and plenty of smiles. Here, I pose with the </em>l<em>ucky winners and their gift cards.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5qoChMUdaEGIwEdSWZoTXA.png" /></figure><h3>Meaningful conversations and collaboration</h3><p>Our team members George and Rajendran had the opportunity to meet with SACS President Grant Dark and Software Developer Alex Berry to discuss how BoldSign and Bold Reports can help support SACS’s ongoing innovation and client success. These conversations opened doors for deeper collaboration and exciting future possibilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CSCLRYZv_vywsc-uDUSruQ.png" /><figcaption>Rajendran and George from Syncfusion, the company behind BoldSign, met with SACS leadership, Grant Dark and Alex Berry, to explore how BoldSign and Bold Reports can support continued innovation.</figcaption></figure><p>The Syncfusion team — myself, Rajendran, and George — also had the opportunity to connect with event organizer Lacey Carlisle of SACS Software. We told her how impressed we were with how much the event had grown since last year and that we appreciated the time to share the customer video case study during the earlier session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N-nEJAg5O9hIlLXFvmh_bQ.png" /><figcaption>Syncfusion team members with event organizer Lacey Carlisle of SACS Software. A perfect end to a wonderful event. Until next time!</figcaption></figure><h3>Looking ahead with appreciation</h3><p>As the conference ended, our team left feeling inspired and energized by the strong sense of community that defines SACS and its clients. The event was more than a gathering — it was a celebration of partnership, digital innovation, and shared purpose. We’re grateful for the meaningful conversations, new connections, and continued collaboration. Together, SACS and BoldSign are helping organizations simplify their operations, save time, and deliver even better service to the communities they support.</p><h3>Further resources</h3><ul><li>SACS Software: <a href="https://www.sacssoftware.com/">https://www.sacssoftware.com</a></li><li>BoldSign: <a href="https://staging.boldsign.com/">https://www.boldsign.com</a></li><li>BoldSign &amp; SACS Software video case study: <a href="https://www.youtube.com/watch?v=JPNHKAH5WGs&amp;t=2s">https://www.youtube.com/watch?v=JPNHKAH5WGs&amp;t=2s</a></li><li>BoldSign YouTube channel:<a href="https://www.youtube.com/watch?v=JPNHKAH5WGs&amp;t=2s"> https://www.youtube.com/@boldsign</a></li></ul><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 30, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8cfd1b9974d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/sacs-2025-user-conference-a8cfd1b9974d">BoldSign team at the SACS 2025 User Conference: Strengthening Partnerships</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build client Trust with Every Document — Beyond Just Signatures]]></title>
            <link>https://medium.com/boldsign/build-client-trust-with-esignature-docs-1127e82cfe2c?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/1127e82cfe2c</guid>
            <category><![CDATA[esignature-docs]]></category>
            <category><![CDATA[document-automation]]></category>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[document-signing]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 11:11:32 GMT</pubDate>
            <atom:updated>2026-04-08T11:11:30.964Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Build client Trust with Every Document — Beyond Just Signatures" src="https://cdn-images-1.medium.com/max/768/1*gY8XANy5KgNWk2liNBrjyQ.png" /></figure><p>Trust isn’t built at the moment of signing — it begins long before. Every document you send, from proposals to contracts, is a reflection of your professionalism, transparency, and commitment to the client. With <a href="https://boldsign.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign eSignature software</a>, you can turn routine paperwork into meaningful trust-building experiences. Here’s how to make every document count.</p><h3>How Every Document Interaction Builds Client Trust</h3><p>Every document you share with a client, from the first proposal to the final contract, shapes how they perceive your brand. These interactions are not just about completing a transaction. They communicate your standards, attention to detail, and commitment to a smooth and professional experience.</p><p>BoldSign helps you deliver documents that are clear, well-structured, and easy to navigate. Each touchpoint becomes an opportunity to build trust, strengthen collaboration, and demonstrate your expertise well before a signature is added.</p><p>The following are seven practical ways your documents can inspire trust from the very first interaction.</p><h4>1. Communicate Clearly to Eliminate Uncertainty</h4><p>Clients are more likely to trust your business when documents are clear and easy to understand. With BoldSign’s templates, you can use simple language, add helpful notes, and highlight key sections to guide your clients through the content. This clarity reduces confusion, ensures consistent communication, and helps clients feel confident in your services.</p><h4>2. Brand Documents for Lasting Credibility</h4><p>Polished, branded documents signal professionalism. Sloppy formatting or errors can undermine confidence, while sleek designs convey attention to detail. Our branding tools let you <a href="https://support.boldsign.com/kb/article/14437/create-a-brand-in-boldsign?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">incorporate your logo,</a> <a href="https://support.boldsign.com/kb/article/14006/customize-color-scheme-for-branding?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">colors</a>, and <a href="https://support.boldsign.com/kb/article/14221/change-the-email-display-name?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">email domain</a> into every signature request email and document, from quotes to contracts.</p><h4>3. Enhance Trust with Real-Time Visibility</h4><p>Clients hate being left in the dark. The <a href="https://support.boldsign.com/kb/article/96/manage-in-app-notifications?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">real-time tracking</a> and <a href="https://support.boldsign.com/kb/article/14647/information-the-audit-trail-document-contains?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">audit trails</a> in BoldSign provide visibility into every step of the document process, showing when a document was sent, viewed, or signed. For example, a client awaiting a contract can track its progress, eliminating uncertainty. This transparency, combined with the secure audit logs, reassures clients of your accountability and commitment.</p><h4>4. Streamline Collaboration for a Client-Focused Experience</h4><p>When documents involve multiple stakeholders, the way you manage collaboration reflects your commitment to serving client needs. BoldSign supports smooth teamwork through features like <a href="https://support.boldsign.com/kb/article/14992/add-multiple-recipients-for-signature-request?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">multiparty signing</a>, <a href="https://support.boldsign.com/kb/article/562/change-auto-reminder-settings?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">automated reminders</a>, shared templates, and real-time agreement tracking.</p><p>Clients and their teams can review, edit, and sign documents together using collaborative field editing and team-based visibility. With <a href="https://support.boldsign.com/kb/article/42/create-custom-permission?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">custom permissions</a> and workflow transparency, you ensure that every participant stays informed and aligned.</p><h4>5. Personalize Documents for a Deeper Connection</h4><p>Personalizing documents shows clients you care and understand their needs. With BoldSign, you can easily add details like names, project goals, or timelines to make each document feel tailored and relevant.</p><p>Even when sending documents in bulk, BoldSign’s CSV-based Bulk Send feature ensures every client receives a customized version without extra manual work — helping build trust through thoughtful, efficient communication.</p><h4>6. Sustain Trust with Post-Signature Engagement</h4><p>Trust-building extends beyond the signature. Follow-up documents like progress reports or invoices keep clients informed and engaged.</p><p><a href="https://boldsign.com/integrations?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign integrates</a> with productivity and automation tools such as Power Automate, Zapier, and Google Drive, allowing you to automate updates and provide easy access to signed documents. For example, you can automatically generate and send a project milestone report once a document is signed, keeping clients informed and reinforcing your commitment to transparency and ongoing support.</p><h4>7. Prioritize Security for Client Confidence</h4><p>Clients need assurance that their sensitive information is handled with care. BoldSign meets top global standards like <a href="https://boldsign.com/soc2-overview?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">SOC 2</a>, <a href="https://boldsign.com/gdpr-overview?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">GDPR</a>, <a href="https://boldsign.com/hipaa-overview?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">HIPAA</a>, and PCI DSS. Every signature is legally enforceable under the ESIGN Act, eIDAS, and global laws. With AES-256 encryption, your data stays protected from start to finish. By using BoldSign, you demonstrate a strong commitment to data protection — building trust through secure and responsible document handling.</p><h3>Intuitive Document Experiences</h3><p>Documents should feel less like tasks and more like seamless interactions. BoldSign helps you create smooth, intuitive signing experiences that reflect your professionalism and respect for your clients’ time with:</p><ul><li><strong>Mobile-friendly signing</strong>: Clients can review and sign documents from any device using the BoldSign iOS and Android apps.</li><li><strong>Custom signer guidance</strong>: Add clear instructions and field labels to guide clients through complex forms, reducing confusion and improving completion rates.</li><li><strong>Accessibility and ease-of-use</strong>: A clean interface and adaptive layout make documents easy to navigate for all users, including those with limited tech experience.</li></ul><h3>Accelerate Growth with Effortless Document Automation</h3><p>As your client base grows, delivering consistent, trust-building documents should remain an efficient process. Automation capabilities in BoldSign help you maintain quality while freeing your team to focus on client relationships:</p><ul><li><strong>Trigger-Based Document Workflows</strong><br>Automatically send documents when specific actions occur in your connected apps — like a deal closing or a new client onboarding. Using Power Automate or Zapier, you can set up workflows that ensure timely communication and reduce manual effort.</li><li><strong>Scalable Template Libraries</strong><br>Create reusable, multilingual templates to support global clients and maintain consistency across markets. These templates can be used in bulk sends or embedded in automated flows for faster execution.</li><li><strong>Automated Reminders and Expiry Settings</strong><br>Keep your document processes moving with automated reminders for pending signatures and customizable expiry dates. This reduces delays, improves turnaround time, and ensures clients stay engaged without manual follow-ups.</li></ul><h3>BoldSign: Your Partner in Building Trust</h3><p>BoldSign does more than simplify e-signatures — it helps you show up for clients consistently. Templates ensure brand consistency, smart fields enable fast personalization, and collaborative tools eliminate delays, creating a smoother client experience. These features save time while making interactions more transparent and engaging.</p><h3>Conclusion</h3><p>The documents you send are a chance to showcase your commitment to transparency, professionalism, and client success. With BoldSign, you can transform every document interaction into a trust-building moment, from personalized proposals to secure, trackable contracts. Start using BoldSign to elevate your client relationships.</p><p>Ready to turn your documents into trust-building tools? Sign up for <a href="https://account.boldsign.com/signup?planId=1018&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign free trial</a> and see how easy it is to <a href="https://support.boldsign.com/kb/article/15/send-first-document-for-signature?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">create</a>, <a href="https://support.boldsign.com/kb/article/17/signing-as-a-recipient?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">sign</a>, and <a href="https://support.boldsign.com/kb/category/24?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">manage</a> client-focused documents that strengthen relationships.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 31, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1127e82cfe2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/build-client-trust-with-esignature-docs-1127e82cfe2c">Build client Trust with Every Document — Beyond Just Signatures</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step-by-Step Guide to Configure OneLogin for SSO in BoldSign]]></title>
            <link>https://medium.com/boldsign/configure-onelogin-single-sign-on-boldsign-0419c2d7469f?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/0419c2d7469f</guid>
            <category><![CDATA[onelogin]]></category>
            <category><![CDATA[ami]]></category>
            <category><![CDATA[single-sign-on]]></category>
            <category><![CDATA[identity-provider]]></category>
            <category><![CDATA[openid]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 06:46:16 GMT</pubDate>
            <atom:updated>2026-04-06T06:46:15.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Step-by-Step Guide to Configure OneLogin for SSO in BoldSign" src="https://cdn-images-1.medium.com/max/768/1*-_zkM7kBwn6ixTwHnNkbPQ.png" /></figure><p>Single Sign-On (<strong>SSO</strong>) is a powerful feature that simplifies user authentication across multiple applications. By using OneLogin as an <strong>identity provider</strong>, organizations can streamline access management, enhance security, and improve user experience.</p><p>In this guide, we’ll introduce<strong> OneLogin as an Identity Provider (IdP)</strong>, highlight the benefits of integrating it with <strong>BoldSign’s Single Sign-On (SSO)</strong>, and walk you through the steps to configure OneLogin for SSO in the BoldSign application.</p><h3>What is OneLogin as an identity provider?</h3><p><strong>OneLogin</strong> is a cloud-based <strong>Identity and Access Management (IAM)</strong> provider that enables organizations to manage user identities and secure access to applications and data. As an <strong>Identity Provider (IdP)</strong>, OneLogin plays a central role in Single Sign-On (SSO) systems by authenticating users and passing identity information to connected applications like BoldSign.</p><p>It supports protocols like <strong>SAML 2.0, OpenID Connect (OIDC), and OAuth 2.0</strong> to establish trust relationships between the IdP and SPs.</p><h3>What does OneLogin do as an identity provider?</h3><p>As an IdP, OneLogin:</p><ul><li><strong>Authenticates users</strong>: It verifies user credentials (e.g., username and password) and enforces security policies like multi-factor authentication (MFA).</li><li><strong>Issues SAML tokens</strong>: After authentication, OneLogin generates a SAML assertion (token) that contains user identity details and permissions.</li><li><strong>Facilitates SSO</strong>: Users log in once via OneLogin and gain access to multiple connected applications without re-entering passwords.</li><li><strong>Centralizes access control</strong>: Admins can manage user roles, permissions, and access to applications from a single dashboard.</li><li><strong>Supports federation</strong>: OneLogin can integrate with other identity systems, enabling cross-domain authentication.</li></ul><h3>Why use BoldSign SSO with OneLogin?</h3><p>BoldSign SSO offers several benefits:</p><ul><li><strong>Enhanced user experience</strong>: Users can log in to BoldSign using their existing email address, reducing the need to remember multiple passwords and simplifying access.</li><li><strong>Improved security</strong>: OAuth-based authentication reduces the risk of password-related breaches.</li><li><strong>Centralized authentication</strong>: Manage user access from a single identity provider.</li><li><strong>Efficiency</strong>: SSO reduces the need for separate authentication credentials, improving efficiency.</li></ul><h3>Step-by-step: How to set up SSO with OneLogin</h3><p>Follow the steps below to set up SSO with OneLogin in the BoldSign application:</p><h4>1. Create an OpenID App in OneLogin</h4><ul><li>Log in to your <strong>OneLogin</strong> admin account or <a href="https://www.onelogin.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">create an account</a> if you don’t have one.</li><li>Go to <strong>Applications</strong> and click <strong>Add App</strong>.</li></ul><figure><img alt="OneLogin addapp" src="https://cdn-images-1.medium.com/max/1024/1*LWAoEB5t4T6XM65Y6HqQKQ.png" /><figcaption>OneLogin addapp</figcaption></figure><ul><li>Search for <strong>OpenID Connect </strong>(OIDC) and select it.</li></ul><figure><img alt="OneloginOpenID" src="https://cdn-images-1.medium.com/max/1024/1*MWV3pgHq7DoFvxLqrFjKAg.png" /><figcaption>OneloginOpenID</figcaption></figure><ul><li>Click <strong>Save</strong> to add the application.</li></ul><figure><img alt="OneloginSave" src="https://cdn-images-1.medium.com/max/1024/1*0e2hhElnGls853MVaCdBaA.png" /><figcaption>OneloginSave</figcaption></figure><h4>2. Configure OpenID settings in OneLogin</h4><ul><li>Go to the <strong>Configuration</strong> tab.</li></ul><figure><img alt="OneLogin configuration" src="https://cdn-images-1.medium.com/max/1024/1*-0vfaBEOpMSgYYA9ZBu92w.png" /><figcaption>OneLogin configuration</figcaption></figure><ul><li>In the Redirect URI field, enter:</li></ul><p><a href="https://account.boldsign.com/SSOLogin/SSOLoginCallback,"><strong>https://account.boldsign.com/SSOLogin/SSOLoginCallback</strong>,</a> this can be obtained from the BoldSign web app <strong>Settings &gt; Identity Management &gt; SSO</strong>. Then click the <strong>Save</strong> button.</p><figure><img alt="OneLogin RedirectURL" src="https://cdn-images-1.medium.com/max/1024/1*WoagQV_KnRpNdBYjVPWl6w.png" /><figcaption>OneLogin RedirectURL</figcaption></figure><ul><li>Go to the <strong>SSO</strong> tab:</li></ul><p>a. Copy the <strong>Client ID</strong>.</p><p>b. Click <strong>Show client secret</strong> and copy it.</p><p>c. Copy the <strong>Issuer URL</strong> (Authority URL).</p><h4>3. Add a new user</h4><figure><img alt="OneLoginSSO" src="https://cdn-images-1.medium.com/max/1024/1*llfbv8-u-iz8gT4goFa87g.png" /><figcaption>OneLoginSSO</figcaption></figure><ul><li>Go to the<strong> Users</strong> tab in the top navigation.</li><li>Click <strong>New User</strong>.</li></ul><figure><img alt="OneLoginNewuser" src="https://cdn-images-1.medium.com/max/1024/1*nBP6bKyhshiz6w-0trBW9w.png" /><figcaption>OneLoginNewuser</figcaption></figure><ul><li>Fill in the required fields:</li></ul><p>a. <strong>Email </strong>address</p><p>b. <strong>First Name, Last Name</strong></p><p>c. <strong>Username </strong>(can be the same as email)</p><p>d. Assign a <strong>Role</strong> if needed (optional but useful for access control)</p><ul><li>Click the <strong>Save User</strong> button.</li></ul><h4>4. Assign the BoldSign app to the user</h4><ul><li>After saving the user, go to the <strong>Applications</strong> tab under the user profile.</li></ul><figure><img alt="OneLoginUserinfo" src="https://cdn-images-1.medium.com/max/1024/1*Q7Arv01O9TGWNBz3XYev9Q.png" /><figcaption>OneLoginUserinfo</figcaption></figure><ul><li>Click <strong>(+)</strong> to assign an app.</li></ul><figure><img alt="OneLoginplus sign" src="https://cdn-images-1.medium.com/max/1024/1*eMzm-Wc9txY1dMIdSsS1ng.png" /><figcaption>OneLoginplus sign</figcaption></figure><ul><li>Select the <strong>BoldSign OpenID Connect app</strong> you created earlier and click the <strong>Continue</strong> button.</li><li>Then <strong>Save</strong>.</li></ul><figure><img alt="OneLoginAssignapp" src="https://cdn-images-1.medium.com/max/657/1*BPhRkuqqwwPyihZW4PdgmA.png" /><figcaption>OneLoginAssignapp</figcaption></figure><h4>5. Configure SSO in BoldSign</h4><ul><li>Log in to your <a href="https://app.boldsign.com/account/login?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign admin account</a>.</li><li>Navigate to <strong>Settings &gt; Identity Management</strong>.</li><li>In the<strong> Single Sign-On</strong> section, choose <strong>OpenID</strong> as the authentication method.</li><li>Enter the following:</li></ul><p><strong>a. Client ID</strong> (from OneLogin)</p><p><strong>b. Client Secret </strong>(from OneLogin)</p><p><strong>c. Authority URL</strong> (Issuer URL from OneLogin)</p><ul><li>Click <strong>Save</strong> to apply the configuration.</li></ul><figure><img alt="Configure SSO in BoldSign" src="https://cdn-images-1.medium.com/max/1024/1*pqYSC7PEZEzXfdk2kq9CaA.png" /><figcaption>Configure SSO in BoldSign</figcaption></figure><p>Once SSO is configured in BoldSign, the <strong>setup cannot be deleted</strong>. However, you can update the configuration at any time by modifying the <strong>client details, authorization endpoints</strong> as needed.</p><h4>6. Invite the new user to join the BoldSign organization</h4><ul><li>Go to the <strong>Users &amp; Teams &gt; Users</strong> and click the <strong>Invite users</strong> button. Enter the email address (must be associated with OneLogin)&gt; click <strong>Add</strong>, then <strong>Invite</strong> to send the invitation.</li></ul><figure><img alt="Invite users" src="https://cdn-images-1.medium.com/max/1024/1*9GADfYinqT1nk0yedWqobQ.png" /><figcaption>Invite users</figcaption></figure><ul><li>Users receive an email with an invitation link. Clicking the <strong>Accept Invitation</strong> link redirects them to the BoldSign login page.</li></ul><figure><img alt="Accept Invitation link" src="https://cdn-images-1.medium.com/max/494/1*RYsizFIjVGvb_smdxow3UA.png" /><figcaption>Accept Invitation link</figcaption></figure><ul><li>Click the <strong>Log into BoldSign via [Your Organization’s account name]</strong> button to sign in using your organization’s Single Sign-On (SSO) credentials. For example, if your organization’s account name is <strong>Cubeflakes</strong>, the button will read: <strong>Log into BoldSign via Cubeflakes</strong>.</li></ul><figure><img alt="Log into BoldSign via Cubeflakes button" src="https://cdn-images-1.medium.com/max/518/1*_0rWFXSnl3wE8aMIraDa2w.png" /><figcaption>Log into BoldSign via Cubeflakes button</figcaption></figure><ul><li>You will be redirected to the <strong>OneLogin</strong> log in page. Enter your <strong>Credentials</strong> and click the <strong>Continue</strong> button.</li></ul><figure><img alt="OneLogin LogIn page" src="https://cdn-images-1.medium.com/max/479/1*pHx6WCzb2PoDp-TAvmEUiQ.png" /><figcaption>OneLogin LogIn page</figcaption></figure><ul><li>You will be asked if you want to stay signed in. Choose <strong>No or Yes, Keep me signed in</strong>.</li></ul><figure><img alt="Choose No or Yes, Keep me signed in" src="https://cdn-images-1.medium.com/max/349/1*00xM0_g_NXxXHIfcFXEvPA.png" /><figcaption>Choose No or Yes, Keep me signed in</figcaption></figure><ul><li>The sign-in page will be displayed. Click on the <strong>Proceed</strong> button.</li></ul><figure><img alt="The Proceed button" src="https://cdn-images-1.medium.com/max/375/1*mONMforMaGpO6ZCRpHBS4g.png" /><figcaption>The Proceed button</figcaption></figure><ul><li>The new user has successfully joined the BoldSign organization.</li></ul><figure><img alt="Dashboard — BoldSign organization" src="https://cdn-images-1.medium.com/max/1024/1*ikc4mxGVbuurW8mvgbtKMA.png" /><figcaption>Dashboard — BoldSign organization</figcaption></figure><h4>7. Log in using SSO to test the connection</h4><ul><li>Go to the <a href="https://account.boldsign.com/login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D4daff5ba-13fd-45b6-b64d-16c670c4749d%26redirect_uri%3Dhttps%253A%252F%252Fapp.boldsign.com%252Fsignin-oidc%26response_type%3Dcode%26scope%3Dopenid%2520profile%26code_challenge%3DbvMC2xkuEbaiDwwKJi6ExVrIfJRNMNIQhYucFqhgZ-k%26code_challenge_method%3DS256%26nonce%3D638925831894556523.YmU1NGI4YjAtYTM2Yi00N2Y0LTgzN2YtYThmZmE2MDdiYmExZTViZTJlYmYtYzk0NS00MzUxLWEzOWYtOGY2NzM4ZjVmYTQy%26state%3DCfDJ8HLMSoTHWdNLuoRcK_--LnHDhmD8P4BWZl_cZxBpJUBma8sbyRKgqojtKDwehWEM5LwyrI_JnyRnKhcpHF20LiN7J1-KWyo4r7luiwpaUSbg3cpRtHiLfY7Y9c_VQk1gNB3A6O7h7cgo7SHlZIQIn4JX1XyNRU_AjZKWwBDbuIPPJRTPsaXxPCA5aAdUcmpLPj9DN_DuaZhhKjoXExEEQHvdbCK_nPtS9bfdNui5DkAMkdh9aiw1Pc1pHaP36Z_5Z75weYJHXqr0RWHWdusNcrJrUOg7JF9guw8EkUOMgQPX7qH5lcWFhma79SVC__Am8vKTlgDYWTM0rXZFvOwTtCepDwBPu3tEN8Q2FigJ4Q4XWSlc1taDvR1YFxivtjRdGYOeKkomO66LtKdX9ZxgoPWs5VaISa30TLvqRRXPd8d5%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.6.1.0&amp;?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign Login Page</a>.</li><li>Click the <strong>Sign In with SSO</strong> option.</li></ul><figure><img alt="Sign In with SSO option" src="https://cdn-images-1.medium.com/max/328/1*gi6fu40YDGFf7VqsyYWEVg.png" /><figcaption>Sign In with SSO option</figcaption></figure><ul><li>In the <strong>Organization Email</strong> text box, enter the OneLogin user email address associated with the SSO account and click the <strong>Continue </strong>button.</li></ul><figure><img alt="Click the Continue button" src="https://cdn-images-1.medium.com/max/300/1*gvJXAzIX8EBnsn0pYy5wBg.png" /><figcaption>Click the Continue button</figcaption></figure><ul><li>You will be redirected back to the BoldSign <strong>Stay signed in</strong> page. Choose your preferred option by clicking the appropriate button.</li></ul><figure><img alt="Stay signed in page" src="https://cdn-images-1.medium.com/max/307/1*jrRelT8U0XwjD5rvijxlPg.png" /><figcaption>Stay signed in page</figcaption></figure><ul><li>After making your selection, you will be redirected to the BoldSign dashboard.</li></ul><h3>Account requirements</h3><ul><li>The OneLogin account used for SSO must be registered as a user within your organization’s Identity Provider (IdP) setup.</li><li>Only users recognized and authorized by your IdP will be able to authenticate via BoldSign’s SSO integration.</li></ul><h3>Conclusion</h3><p>Integrating BoldSign with OneLogin for SSO is a smart move for organizations looking to simplify access control and boost security. With just a few configuration steps, your team can enjoy a smooth and secure login experience.</p><p>Ready to get started? Sign up for a <a href="https://account.boldsign.com/signup?planId=1076&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">30-day free trial account </a>and explore <a href="https://boldsign.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign’s powerful features</a>.</p><p>We’d love to hear from you! Share your thoughts in the comments section below. Need help? Reach out via our <a href="https://support.boldsign.com/support/tickets/create?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">support portal</a> or schedule a personalized <a href="https://boldsign.com/request-demo?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">demo</a> with our team.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 23, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0419c2d7469f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/configure-onelogin-single-sign-on-boldsign-0419c2d7469f">Step-by-Step Guide to Configure OneLogin for SSO in BoldSign</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When to Use BoldSign Bulk Links to Simplify Bulk Signing]]></title>
            <link>https://medium.com/boldsign/when-to-use-bulk-links-boldsign-guide-85c3e8b8105d?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/85c3e8b8105d</guid>
            <category><![CDATA[collect-signatures]]></category>
            <category><![CDATA[e-signing]]></category>
            <category><![CDATA[bulk-signing]]></category>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[bulk-link]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Mon, 06 Apr 2026 06:45:04 GMT</pubDate>
            <atom:updated>2026-04-06T06:45:03.080Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="When to Use BoldSign Bulk Links to Simplify Bulk Signing" src="https://cdn-images-1.medium.com/max/768/1*akChHyR5qOZHR3GJFjNZ7A.png" /></figure><p>BoldSign bulk signing links are a powerful way to streamline the process of collecting signatures from multiple recipients. Unlike traditional e-signing methods that require sending individual documents to each signer, BoldSign allows you to create a single link that can be shared with many recipients. This makes it ideal for situations where speed, flexibility, and scalability are essential — especially when managing high-volume or repetitive signing tasks.</p><p>This blog explores when to use BoldSign bulk signing links and practical applications to help you decide when they are the best fit for your needs.</p><h3>What are BoldSign bulk signing links?</h3><p><a href="https://support.boldsign.com/kb/article/22/creating-bulk-links?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign bulk links</a> enable you to create a single signing link for a document or template that can be shared with multiple recipients. Each recipient who accesses the link can sign their own copy of the document, making it an efficient solution for collecting signatures at scale. These links offer enhanced flexibility, security features like email verification, and powerful management tools to help you stay organized and in control.</p><h3>When to use BoldSign bulk signing links</h3><p>Bulk signing links are perfect for collecting signatures from many people quickly and efficiently. Here are eight key scenarios where they’re especially useful.</p><h4>1. Mass signature collection</h4><p>When you need multiple individuals to sign the same document, such as NDAs or consent forms, bulk links simplify the process. Instead of sending individual emails, you can <a href="https://support.boldsign.com/kb/article/14073/create-bulk-links?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">share a single link</a> via email, social media, or your website, allowing recipients to access and sign the document at their convenience.</p><h4>2. When you want direct website integration</h4><p><a href="https://support.boldsign.com/kb/article/22/creating-bulk-links?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign bulk links</a> can be embedded directly into websites, making them ideal for scenarios where users need to sign documents as part of an online process. For example, on a training website, you can embed a bulk link for a feedback survey form, allowing employees to sign and submit their feedback immediately after completing a training session.</p><h4>3. Flexible and scalable workflows</h4><p>BoldSign bulk links are ideal when you need flexibility in your signing process. You can <a href="https://support.boldsign.com/kb/article/17726/create-bulk-links-using-templates?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">use predefined templates</a> for consistency or upload a document for one-time use, adapting to your specific workflow. Additionally, you can <a href="https://support.boldsign.com/kb/article/13985/how-to-add-additional-roles-in-bulk-link?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">customize signer roles</a>, making it suitable for both small and large-scale signing needs.</p><h4>4. When document expiration is not needed</h4><p>BoldSign allows you to <a href="https://support.boldsign.com/kb/article/19720/is-it-possible-to-prevent-a-bulk-link-from-expiring-in-boldsign?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">disable expiration for bulk signing links</a>, ensuring that documents remain accessible indefinitely. This is particularly useful for ongoing processes where signatures are needed over an extended period without having to regenerate links.</p><h4>5. Limit signers with response controls</h4><p>With BoldSign bulk links, <a href="https://support.boldsign.com/kb/article/14080/limit-signers-in-bulk-link?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">you can set a specific number of required responses</a>, giving you control over how many signatures the link will accept. This is useful for limiting participation to a predefined group or ensuring a specific number of submissions.</p><h4>6. Secure signing with verification options</h4><p>When security and verification are critical, BoldSign bulk links offer robust features like <a href="https://support.boldsign.com/kb/article/15962/how-to-create-regular-expressions-regex-for-email-address-validation?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">email validation</a> to ensure only intended recipients can access and sign documents. You can also configure authentication methods and set signing orders to maintain an organized and secure workflow.</p><h4>7. Dynamic and editable signing needs</h4><p>BoldSign bulk links allow you to <a href="https://support.boldsign.com/kb/article/16232/how-to-edit-the-existing-bulk-link?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">edit</a> or <a href="https://support.boldsign.com/kb/article/14245/deactivate-bulk-link?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">deactivate</a> links after creation, providing flexibility to adapt to changing requirements. You can also enable signers to reassign signature requests, which is useful when the initial recipient is not the appropriate signer.</p><h4>8. Efficient document management</h4><p>For scenarios requiring efficient document management, BoldSign allows you to <a href="https://support.boldsign.com/kb/article/552/signed-bulk-link-document-download?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">download signed documents individually</a> or <a href="https://support.boldsign.com/kb/article/19721/how-to-download-attachments-in-bulk-links?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">in bulk</a> and delete them from the platform after downloading. This keeps your document repository organized and clutter-free.</p><h3>How to get started with BoldSign bulk links</h3><p>BoldSign simplifies bulk signing with a fast and customizable setup process. You can tailor each step to match your workflow, from link creation to signer configuration and security settings.</p><h4>Creating and managing bulk signing links</h4><p>Creating and managing bulk signing links in BoldSign is simple and flexible. Here’s a step-by-step guide:</p><p><strong>1. Create the bulk link</strong></p><ul><li>Go to your BoldSign dashboard.</li><li>Click <strong>Create New</strong> and Select <strong>Create Bulk Link</strong>.</li></ul><figure><img alt="Create new bulk link option" src="https://cdn-images-1.medium.com/max/1024/1*UTza-PEYi6nm0oI-IUopPg.png" /><figcaption>Create new bulk link option</figcaption></figure><p>Alternatively, you can go to the <strong>My Bulk Links</strong> page and click <strong>New Bulk Link</strong> to start the process. You can also create a bulk link from the <a href="https://support.boldsign.com/kb/article/17726/create-bulk-links-using-templates?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">All Templates or My Templates sections</a> by locating the desired template and selecting <strong>Create Bulk Link</strong> from its action menu.</p><p><strong>2. Prepare the bulk link document</strong></p><ul><li>Enter a <strong>title</strong> for your bulk link.</li><li>Add a <strong>welcome message</strong> and an <strong>acknowledgment message</strong> to guide signers.</li><li><strong>Upload a document</strong> or <strong>select a template</strong> using the <strong>Browse Templates</strong> option.</li><li>Assign the <strong>initiator role</strong> and choose the <strong>signer language</strong>, if needed.</li><li>To add more required roles, click the <strong>Add Recipient Role</strong> button and enter the details for the new role.</li></ul><figure><img alt="Enter bulk link details" src="https://cdn-images-1.medium.com/max/1024/1*DEYz-m2UZgTi2iU4pWaL5g.gif" /><figcaption>Enter bulk link details</figcaption></figure><p><strong>3. Configure bulk link settings</strong></p><p>Set options such as:</p><ul><li><strong>Allow signers to sign multiple times.</strong></li><li><strong>Limit the number of responses.</strong></li><li><strong>Enable email validation.</strong></li><li><strong>Set expiration date </strong>or<strong> disable it to create a non-expiring bulk link</strong>.</li></ul><figure><img alt="Configure bulk link settings" src="https://cdn-images-1.medium.com/max/1024/1*m9KcZtJjBmMV7Axr9uv9BQ.png" /><figcaption>Configure bulk link settings</figcaption></figure><p>In the <strong>Document Settings</strong>, you can:</p><ul><li>Select a <strong>brand</strong>.</li><li>Allow <strong>signer reassignment</strong>.</li><li>Set <strong>auto-reminders</strong>.</li></ul><figure><img alt="Document settings" src="https://cdn-images-1.medium.com/max/1024/1*PCoXPDsfpo2SyhAb5x5ddg.png" /><figcaption>Document settings</figcaption></figure><p><strong>4. Add form fields</strong></p><ul><li>On the <strong>Configure Fields</strong> page, add or adjust the required fields for signing.</li><li>You can customize fields even if you’re using a template.</li></ul><figure><img alt="Configure form fields" src="https://cdn-images-1.medium.com/max/1024/1*jXbDUbqyEN0B3001J-O7ig.png" /><figcaption>Configure form fields</figcaption></figure><p><strong>5. Create and share the link</strong></p><p>a. Click <strong>Create Bulk Link</strong>.</p><p>b. You’ll receive:</p><ul><li>A <strong>URL</strong> to share with signers via email, social media, or any other messaging app.</li><li>An <strong>embed code</strong> for web integration.</li></ul><figure><img alt="Bulk signing link URL and embed code" src="https://cdn-images-1.medium.com/max/589/1*Sxarisgjb8FWJ50m6hm8dg.png" /><figcaption>Bulk signing link URL and embed code</figcaption></figure><p><strong>6. Monitor and manage</strong></p><p>Go to the <a href="https://support.boldsign.com/kb/article/13180/manage-bulk-link?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign My Bulk Links page</a>, where you can:</p><ul><li>Track who has signed.</li><li>Edit or deactivate the link.</li><li>Download signed documents.</li><li>Delete documents to keep your dashboard organized.</li></ul><figure><img alt="Manage bulk signing links" src="https://cdn-images-1.medium.com/max/1024/1*pLvyGeJuezeFxD9cR-yeHA.png" /><figcaption>Manage bulk signing links</figcaption></figure><h4>Signing Process with BoldSign bulk links</h4><p>The signing process is user-friendly and secure:</p><ul><li><strong>Access the link</strong>: Recipients open the bulk link from any device.</li><li><strong>Enter details</strong>: Signers provide their name and email address.</li></ul><figure><img alt="Enter signer’s details" src="https://cdn-images-1.medium.com/max/713/1*6ADYCJBlms-QGKRB7tMSpQ.png" /><figcaption>Enter signer’s details</figcaption></figure><h4>Email verification</h4><ul><li><strong>If email verification is not enabled</strong>: The signer can directly access the document after entering their details.</li><li><strong>If email verification is enabled</strong>: The signer must verify their email address before accessing the document. An OTP is sent to their inbox. Only after entering the OTP can they proceed to review and sign the document.</li></ul><figure><img alt="Email authentication required" src="https://cdn-images-1.medium.com/max/739/1*-q8yG_HK18D4GPE-hgkcLQ.png" /><figcaption>Email authentication required</figcaption></figure><ul><li><strong>Review and sign</strong>: Signers review the document, fill in required fields, and submit their signatures.</li><li><strong>Completion</strong>: The signed document is stored in the BoldSign dashboard for easy access.</li></ul><h3>Conclusion</h3><p>BoldSign bulk signing links offer a smart, scalable solution for collecting signatures efficiently across a wide range of use cases. Whether you’re managing event registrations or feedback surveys, bulk links simplify the process by allowing multiple recipients to sign their own copy through a single shared link.</p><p>With features like non-expiring links, customizable response limits, editable signer roles, and advanced security options, BoldSign empowers teams to streamline workflows and reduce manual effort.</p><p><a href="https://account.boldsign.com/signup?planId=1018&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Sign up for a free 30-day trial</a> on the <a href="https://boldsign.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign website</a> or <a href="https://boldsign.com/request-demo?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">request a demo</a> to see it in action.</p><p>We’d love your feedback! Share your thoughts or suggest topics for future posts in the comments below.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 13, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85c3e8b8105d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/when-to-use-bulk-links-boldsign-guide-85c3e8b8105d">When to Use BoldSign Bulk Links to Simplify Bulk Signing</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adding Hyperlinks in eSignatures: A Complete Guide with BoldSign]]></title>
            <link>https://medium.com/boldsign/add-hyperlinks-in-esignatures-guide-05cf5ae3592d?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/05cf5ae3592d</guid>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[add-hyperlinks]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 10:12:46 GMT</pubDate>
            <atom:updated>2026-03-31T10:12:44.700Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Adding Hyperlinks in eSignatures: A Complete Guide with BoldSign" src="https://cdn-images-1.medium.com/max/768/1*ErmB0UO7vzkK3Y6CDpXkUA.png" /></figure><p>Electronic signature software has evolved beyond simply signing documents. It now enables efficient, interactive, and user-friendly workflows. Hyperlink fields in BoldSign are a feature that contributes to this. They allow users to embed clickable links in eSignature documents.</p><p>In this blog, we’ll explore hyperlinks in eSignature workflows and provide a step-by-step guide to adding them in BoldSign.</p><h3>Introduction to hyperlinks in eSignature software</h3><p>Hyperlinks bring interactivity to eSignature documents, making them more than just static forms. With the BoldSign hyperlink field, senders can embed clickable links that guide signers to:</p><ul><li><strong>Webpages</strong>: Such as terms and conditions, product pages, or help centers.</li><li><strong>Downloadable files</strong>: Like brochures, invoices, or contracts.</li><li><strong>Email clients or phone dialers</strong>: For instant communication with support or sales teams.</li></ul><p>By embedding links, documents become gateways to information, reducing friction and improving clarity.</p><h3>What the BoldSign hyperlink feature provides</h3><p>The BoldSign hyperlink field transforms static eSignature documents into engaging, action-oriented tools. Here’s what it offers:</p><ul><li><strong>Versatile link types</strong>: Supports URLs for webpages, files, email addresses, and phone numbers.</li><li><strong>Smooth integration</strong>: Signers can click links to instantly access webpages, open email clients, or dial phone numbers.</li><li><strong>Customizable appearance</strong>: Adjust font style, size, line height, and color to match your document’s aesthetics or branding.</li><li><strong>Improved conversion</strong>: Drive traffic to landing pages, contact forms, or resources to increase engagement and action.</li><li><strong>Enhanced clarity</strong>: Provide direct access to supporting documents or instructions, reducing confusion.</li><li><strong>Professional presentation</strong>: Create modern, interactive documents that just work.</li><li><strong>Cross-platform compatibility</strong>: Links work seamlessly across devices, ensuring a consistent signer experience.</li></ul><p>By allowing senders to embed clickable links, BoldSign transforms documents into dynamic tools that connect, inform, and convert.</p><h3>How to use BoldSign hyperlinks: step-by-step guide</h3><p><a href="https://support.boldsign.com/kb/article/140/add-hyperlink-field?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Adding a hyperlink</a> in <a href="https://boldsign.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign</a> is intuitive and efficient. Follow these steps:</p><h4>1. Create a new document</h4><ul><li>From the BoldSign dashboard, click <strong>Create New</strong> and select <strong>Create New Document</strong>.</li></ul><figure><img alt="Create new document" src="https://cdn-images-1.medium.com/max/1024/1*Xd1ACva-5rWDEqYOInUyMQ.png" /><figcaption>Create new document</figcaption></figure><ul><li>On the Prepare document page, fill in all the required details and click <strong>Next.</strong></li></ul><figure><img alt="Prepare document page" src="https://cdn-images-1.medium.com/max/1024/1*oODf4jIqC0FafJTzPhymYg.png" /><figcaption>Prepare document page</figcaption></figure><h4>2. Configure the hyperlink field</h4><ul><li>On the Configure fields page, locate the <strong>Hyperlink</strong> field in the left panel.</li><li>Drag and drop it at the desired location in the document.</li><li>Once the hyperlink field is added, the settings panel will appear on the right. Set the following:</li></ul><p><strong>Text to display</strong>: Enter the clickable text.</p><p><strong>Hyperlink URL</strong>: Select the link type (URL, email, or phone) and enter the destination. For example, if you select the URL option, you must enter a valid link to a webpage or file.</p><p>Adjust the font family, style, size, line height, and color to match the document’s design.</p><figure><img alt="Add hyperlink field to the document" src="https://cdn-images-1.medium.com/max/1024/1*kfREXXeK0QRbQ4L868mWFw.gif" /><figcaption>Add hyperlink field to the document</figcaption></figure><h4>3. Send the document</h4><ul><li>Once all fields are configured, click Send to deliver the document with the embedded hyperlink to the recipient.</li><li>Signers can then interact with the hyperlink, which directs them to the specified destination.</li></ul><figure><img alt="Hyperlink visible to signer" src="https://cdn-images-1.medium.com/max/1024/1*GA1RJV1k-emZuNWMnuV13Q.png" /><figcaption>Hyperlink visible to signer</figcaption></figure><h3>Conclusion</h3><p><a href="https://support.boldsign.com/kb/article/140/add-hyperlink-field?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign hyperlink fields</a> help turn eSignature documents into interactive tools. With support for multiple link types and customizable design, it enhances clarity, streamlines communication, and boosts engagement. Whether you’re linking to a webpage, contact information, or downloadable resources, BoldSign makes it easy to create smarter, more dynamic documents.</p><p>Ready to enhance your eSignature workflows? Try adding a hyperlink in your next BoldSign document and experience the difference. If you’re not yet using it, <a href="https://account.boldsign.com/signup?planId=1018&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">sign up for a free 30-day trial</a> on the <a href="https://boldsign.com/?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign website</a> or <a href="https://boldsign.com/request-demo?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">request a demo</a> to see it in action.</p><p>We’d love your feedback! Share your thoughts or suggest features you’d like to see added to the platform in the comments below.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 9, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05cf5ae3592d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/add-hyperlinks-in-esignatures-guide-05cf5ae3592d">Adding Hyperlinks in eSignatures: A Complete Guide with BoldSign</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Set Up SSO with Google for Centralized Login]]></title>
            <link>https://medium.com/boldsign/sso-with-google-boldsign-setup-guide-396120c3c889?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/396120c3c889</guid>
            <category><![CDATA[single-sign-on]]></category>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[google-cloud-identity]]></category>
            <category><![CDATA[openid-connect]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 10:12:31 GMT</pubDate>
            <atom:updated>2026-03-31T10:12:29.771Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to Set Up SSO with Google for Centralized Login" src="https://cdn-images-1.medium.com/max/768/1*sZKEGopJZXIh_7hSBmnlXA.png" /></figure><p>Single sign-on (SSO) simplifies and secures authentication across platforms. By integrating Google Cloud Identity or Google Workspace as an identity provider (IdP), BoldSign users can log in with their existing Google accounts, eliminating the need to manage separate credentials.</p><p>This reduces login friction, accelerates easy onboarding, and enhances security through OAuth 2.0 and OpenID Connect (OIDC). It also gives administrators centralized control over access, ensuring policies are enforced consistently.</p><p>In this guide, we’ll cover what Google Cloud Identity is, the advantages of connecting it with BoldSign SSO, the steps to set up the integration, and the account requirements for a smooth login experience.</p><h3>Why use BoldSign SSO with Google?</h3><p>Here are just a few of the benefits of using BoldSign SSO with Google:</p><ul><li><strong>Enhanced user experience</strong>: Log in with a single click using a Google account.</li><li><strong>Improved security</strong>: OAuth and OIDC protocols reduce password risks.</li><li><strong>Centralized management</strong>: Admins manage access through Google Workspace.</li><li><strong>Operational efficiency</strong>: No extra credentials for users to maintain.</li></ul><h3>Step-by-step guide: Connecting BoldSign SSO with Google</h3><h4>Step 1: Configure Google as the identity provider</h4><ol><li>Access Google Cloud Console.</li></ol><p>Go to <a href="https://console.cloud.google.comutm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs/">Google Cloud Console</a>. If you already have a Google account — a Google Workspace or personal Gmail — sign in.If you don’t have a Google account, click <strong>Create account</strong> and follow the prompts to set up either:</p><ul><li>A Google Workspace account (recommended for organizations allows domain-level control and user management).</li><li>Or a personal Google account (suitable for testing or individual use).</li></ul><p>2. Create a new project.</p><ul><li>Select <strong>My First Project</strong>.</li></ul><figure><img alt="Select My First Project" src="https://cdn-images-1.medium.com/max/1024/1*zUDwomc1KU3dYbgfoEmPQQ.png" /><figcaption>Select My First Project</figcaption></figure><ul><li>A dialog box will appear. Select <strong>New Project</strong>.</li></ul><figure><img alt="Select New Project" src="https://cdn-images-1.medium.com/max/1024/1*xCJ7StSStXw-nV1leJz3YQ.png" /><figcaption>Select New Project</figcaption></figure><ul><li>Name your project and select <strong>Create</strong>.</li></ul><figure><img alt="Name your project and select Create" src="https://cdn-images-1.medium.com/max/1024/1*XvfEY-F6uNGifFHD924ayQ.png" /><figcaption>Name your project and select Create</figcaption></figure><p>3. Enable OAuth consent.</p><ul><li>Go to <strong>APIs &amp; Services &gt; OAuth consent &gt; Overview</strong>.</li><li>Fill in details like the app name and support email.</li></ul><figure><img alt="Enable OAuth consent" src="https://cdn-images-1.medium.com/max/1024/1*8l7zVBb-vn3W-v1ggquhJw.png" /><figcaption>Enable OAuth consent</figcaption></figure><ul><li>Choose <strong>External</strong> for public apps or <strong>Internal</strong> for Workspace.</li></ul><figure><img alt="Choose External for public apps or Internal for Workspace" src="https://cdn-images-1.medium.com/max/1024/1*ex_VpbDcPBlkmRD_-cXKCQ.png" /><figcaption>Choose External for public apps or Internal for Workspace</figcaption></figure><ul><li>Add your contact information.</li></ul><figure><img alt="Add your contact information" src="https://cdn-images-1.medium.com/max/1024/1*0XlzWmRzn0ted2ukTkO8sw.png" /><figcaption>Add your contact information</figcaption></figure><p>4. Create OAuth credentials.</p><ul><li>Go to <strong>APIs &amp; Services &gt; Credentials &gt; Create Credentials &gt; OAuth client ID</strong>.</li></ul><figure><img alt="Create OAuth credentials" src="https://cdn-images-1.medium.com/max/1024/1*88eni8LoSpV82KkGRJyCNA.png" /><figcaption>Create OAuth credentials</figcaption></figure><ul><li>Select <strong>Web application</strong> as the application type.</li></ul><figure><img alt="Select Web application" src="https://cdn-images-1.medium.com/max/1024/1*BFZJtlBqUp6efp1BzboBcA.png" /><figcaption>Select Web application</figcaption></figure><ul><li>Under <strong>Authorized redirect URIs</strong>, enter the Redirect URL from the BoldSign application SSO settings.</li></ul><figure><img alt="Enter the Redirect URL from the BoldSign application SSO settings" src="https://cdn-images-1.medium.com/max/1024/1*UsJt5vzhhKdGmEXtP8HYJg.png" /><figcaption>Enter the Redirect URL from the BoldSign application SSO settings</figcaption></figure><figure><img alt="Authorized redirect URIs" src="https://cdn-images-1.medium.com/max/1024/1*2HV9fK3LV1aO2W0_zTCbRQ.png" /><figcaption>Authorized redirect URIs</figcaption></figure><ul><li>Save and note your <strong>Client ID</strong> and <strong>Client Secret</strong>.</li></ul><p>5. Add users.</p><ul><li>Click on the <strong>APIs &amp; Services &gt; OAuth consent screen &gt; Audience</strong>.</li><li>Navigate to the <strong>Test Users</strong> section, select <strong>Add users</strong>, and add your users’ email addresses.</li></ul><figure><img alt="Add users" src="https://cdn-images-1.medium.com/max/1024/1*8Tu-jIyYJtZV_2bQpJS5zw.png" /><figcaption>Add users</figcaption></figure><h4>Step 2: Configure SSO in BoldSign</h4><ol><li>Log in to BoldSign. Go to <strong>Settings &gt; Identity Management &gt; Single</strong> <strong>Sign‑On</strong>.</li><li>Select OAuth as the SSO method.</li><li>Enter Google OAuth details.</li></ol><ul><li><strong>Client ID</strong>: From Google Cloud</li><li><strong>Client Secret</strong>: From Google Cloud</li><li><strong>Token endpoint</strong>: From Google Cloud</li><li><strong>Authentication endpoint</strong>: From Google Cloud</li><li><strong>User information endpoint</strong>: <a href="https://accounts.google.com/">https://accounts.google.com</a></li></ul><p>4. Save the configuration.</p><figure><img alt="Configure SSO in BoldSign" src="https://cdn-images-1.medium.com/max/1024/1*uaM5UCdULrPN29Or0-MZBA.png" /><figcaption>Configure SSO in BoldSign</figcaption></figure><p>Once SSO is configured in BoldSign, the setup cannot be deleted. However, you can update the configuration at any time by modifying the client details and authorization endpoints as needed.</p><h4>Step 3: Invite the new user to join the BoldSign organization</h4><ol><li>Go to <strong>Users &amp; Teams &gt; Users</strong> and select <strong>Invite users</strong> to invite the user you created in Google user management.</li></ol><figure><img alt="Select Invite users" src="https://cdn-images-1.medium.com/max/1024/1*uY_KvBfs5JTFQMMbnreJCg.png" /><figcaption>Select Invite users</figcaption></figure><p>2. Select <strong>Accept Invitation</strong> in the email that is sent.</p><figure><img alt="Select Accept Invitation" src="https://cdn-images-1.medium.com/max/577/1*BbC14WApZRHHAjV8RoWQ9Q.png" /><figcaption>Select Accept Invitation</figcaption></figure><p>3. Select <strong>Log into BoldSign via X</strong> button to log in using your organization’s SSO credentials.</p><figure><img alt="Select Log into BoldSign via X button" src="https://cdn-images-1.medium.com/max/530/1*GgBDjyFeFFIFU6qnVev4yA.png" /><figcaption>Select Log into BoldSign via X button</figcaption></figure><p>4. You will be asked if you want to stay signed in. Choose <strong>No</strong> or <strong>Yes, keep me signed in</strong>.</p><figure><img alt="Choose No or Yes, keep me signed in" src="https://cdn-images-1.medium.com/max/349/1*HUwN2fv2T_dtF73U0AnABA.png" /><figcaption>Choose No or Yes, keep me signed in</figcaption></figure><p>5. The sign-in page will be displayed. Select <strong>Proceed</strong>.</p><figure><img alt="Select Proceed" src="https://cdn-images-1.medium.com/max/375/1*6oAPmkXDNo_MKbHVh9dKeg.png" /><figcaption>Select Proceed</figcaption></figure><p>6. The new user has successfully joined the BoldSign organization.</p><figure><img alt="The new user has successfully joined the BoldSign organization" src="https://cdn-images-1.medium.com/max/1024/1*APpILGLYw0-SCTc0KiNGcw.png" /><figcaption>The new user has successfully joined the BoldSign organization</figcaption></figure><h3>How to sign in with SSO in BoldSign</h3><ol><li>Go to the <a href="https://account.boldsign.com/login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3D4daff5ba-13fd-45b6-b64d-16c670c4749d%26redirect_uri%3Dhttps%253A%252F%252Fapp.boldsign.com%252Fsignin-oidc%26response_type%3Dcode%26scope%3Dopenid%2520profile%26code_challenge%3DbvMC2xkuEbaiDwwKJi6ExVrIfJRNMNIQhYucFqhgZ-k%26code_challenge_method%3DS256%26nonce%3D638925831894556523.YmU1NGI4YjAtYTM2Yi00N2Y0LTgzN2YtYThmZmE2MDdiYmExZTViZTJlYmYtYzk0NS00MzUxLWEzOWYtOGY2NzM4ZjVmYTQy%26state%3DCfDJ8HLMSoTHWdNLuoRcK_--LnHDhmD8P4BWZl_cZxBpJUBma8sbyRKgqojtKDwehWEM5LwyrI_JnyRnKhcpHF20LiN7J1-KWyo4r7luiwpaUSbg3cpRtHiLfY7Y9c_VQk1gNB3A6O7h7cgo7SHlZIQIn4JX1XyNRU_AjZKWwBDbuIPPJRTPsaXxPCA5aAdUcmpLPj9DN_DuaZhhKjoXExEEQHvdbCK_nPtS9bfdNui5DkAMkdh9aiw1Pc1pHaP36Z_5Z75weYJHXqr0RWHWdusNcrJrUOg7JF9guw8EkUOMgQPX7qH5lcWFhma79SVC__Am8vKTlgDYWTM0rXZFvOwTtCepDwBPu3tEN8Q2FigJ4Q4XWSlc1taDvR1YFxivtjRdGYOeKkomO66LtKdX9ZxgoPWs5VaISa30TLvqRRXPd8d5%26x-client-SKU%3DID_NET8_0%26x-client-ver%3D8.6.1.0&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign login page</a>.</li><li>Select <strong>Sign In with SSO</strong>.</li></ol><figure><img alt="Select Sign In with SSO" src="https://cdn-images-1.medium.com/max/328/1*4vby2_1a0fDUNFmha24etA.png" /><figcaption>Select Sign In with SSO</figcaption></figure><p>3. In the <strong>Organization Email</strong> text box, enter the Google Workspace or Gmail address linked to your SSO account and click <strong>Continue</strong>.</p><figure><img alt="Click Continue" src="https://cdn-images-1.medium.com/max/300/1*gvJXAzIX8EBnsn0pYy5wBg.png" /><figcaption>Click Continue</figcaption></figure><p>4. You will be directed to the Google login page. Enter your Google Workspace or Gmail account information.</p><p>5. You will be directed back to BoldSign. Select the button of your choice.</p><figure><img alt="Select No or Yes, Keep me signed in" src="https://cdn-images-1.medium.com/max/307/1*MXiD6SkCD6AXzN1q1VkTIA.png" /><figcaption>Select No or Yes, Keep me signed in</figcaption></figure><p>After successful authentication, you’ll be redirected to the BoldSign dashboard.</p><h3>Account requirements</h3><p>The Google account used for SSO must be added as a user in your organization’s IdP account.</p><ul><li>If you’re using Google Workspace, the account should be part of your organization’s domain and managed under your Workspace admin console.</li><li>Only accounts recognized by your IdP will be able to authenticate through BoldSign SSO.</li><li>For testing, you can use a personal Gmail account, but in production, always use a Workspace account for security and centralized management.</li></ul><h3>Conclusion</h3><p>Integrating Google with BoldSign SSO streamlines access for users and centralizes control for administrators. Employees can sign in with their existing Google Workspace or Gmail accounts, reducing password fatigue while strengthening security.</p><p>Ready to get started? Sign up for a <a href="https://account.boldsign.com/signup?planId=1076&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">30-day free trial account</a> and explore powerful <a href="https://boldsign.com/electronic-signature-featuresutm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">BoldSign features</a>.</p><p>We’d love to hear from you! Share your thoughts in the comments section below. Need help? Reach out via our <a href="https://support.boldsign.com/support/tickets/create?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">support portal</a> or schedule a personalized <a href="https://boldsign.com/request-demo?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">demo</a> with our team.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 8, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=396120c3c889" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/sso-with-google-boldsign-setup-guide-396120c3c889">How to Set Up SSO with Google for Centralized Login</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BoldSign’s Dedicated Australian Data Center is Now Live!]]></title>
            <link>https://medium.com/boldsign/boldsign-data-center-australia-overview-d6c74632787c?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/d6c74632787c</guid>
            <category><![CDATA[au-region]]></category>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[australia-data-center]]></category>
            <category><![CDATA[electronic-signatures]]></category>
            <category><![CDATA[australian-data-center]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 06:02:58 GMT</pubDate>
            <atom:updated>2026-03-30T06:02:57.064Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*_i0-dUUj0-lU1u-i8EpifQ.png" /></figure><p>The launch of the <strong>BoldSign Australia data center</strong> marks another major milestone in our global expansion. With dedicated data centers now available in the US, Europe, Canada, and now in Australia, BoldSign continues to strengthen its worldwide infrastructure — helping businesses manage and sign documents securely, efficiently, and closer to where they operate.</p><h3>Why an Australia data center matters</h3><p>The new BoldSign <strong>Australia data center</strong> enhances service performance and gives customers more control over where their data is stored. By hosting data closer to the region, BoldSign delivers a faster, more reliable, and secure eSignature experience for organizations that operate or have business in Australia.</p><p>The <strong>Australian data center</strong> ensures that organizations meet regional data residency and privacy expectations while enjoying improved speed and reliability for document workflows.</p><h3>Key advantages include</h3><ul><li><strong>Data sovereignty and legal control</strong>: Customers can choose to store their data within Australia, maintaining full control and ensuring it remains under local jurisdiction.</li><li><strong>Enhanced trust and local commitment</strong>: Establishing a dedicated data center in Australia reinforces BoldSign’s commitment to supporting customers with operations in the region, providing reliable infrastructure backed by transparent data practices.</li><li><strong>Legal protection</strong>: Keeping data within national borders gives businesses greater assurance and peace of mind, knowing their documents are managed under local oversight and protection standards.</li><li><strong>Compliance and local assurance</strong>: The Australian data center aligns with Australian data privacy and protection principles, ensuring compliance with local regulations and global security standards. Businesses can confidently manage eSignature workflows knowing their data remains compliant and within the region.</li></ul><h3>Who benefits from the Australia data center</h3><p>The data center in Australia supports a wide range of organizations that manage or process documents within the region. It provides faster access, improved reliability, and localized data control for both regional and global operations.</p><p><strong>Businesses with operations in Australia</strong>: Companies with offices, clients, or teams in Australia can now host and manage their eSignature workflows locally, ensuring smoother performance and enhanced responsiveness</p><p><strong>Global enterprises</strong>: Organizations operating across multiple regions can optimize their BoldSign setup by selecting <strong>Australia</strong> as a preferred data location for local transactions and customer interactions.</p><h3>How to get started</h3><p>When signing up, customers in Australia — and anywhere else — can now choose the <strong>AU region</strong> from a dropdown during the signup process. This ensures your data is hosted within <strong>Australia</strong> from the start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/733/1*xj3xU9pTQEQDzk-fZKFsJA.png" /><figcaption>sign up</figcaption></figure><h3>FAQ</h3><p><strong>Why did BoldSign launch a data center in Australia?</strong></p><p>This expansion ensures customers can store and process their documents closer to where they operate, improving performance, reliability, and data control.</p><p><strong>Who can use the Australia Data Center?</strong></p><p>Any BoldSign customer — whether based in Australia or conducting business in the region — can choose to host their data within the Australia Data Center.</p><p><strong>How do I select the Australia region for my account?</strong></p><p>During signup or migration, customers can choose “AU” as their preferred region. Once selected, all data and documents will be securely stored within Australia</p><h3>Conclusion</h3><p>The launch of the BoldSign <strong>Australia data center</strong> reinforces our commitment to providing faster, more reliable, and secure eSignature experiences for businesses operating in or with Australia.</p><p>As we continue expanding our global infrastructure, BoldSign remains dedicated to empowering organizations to manage and sign documents securely, efficiently, and in full compliance — wherever they do business.</p><p>Have questions or need assistance setting up your account? <a href="https://boldsign.com/contact-us?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Contact our support team</a> — we’re here to help every step of the way.</p><p>Ready to get started? <a href="https://account.boldsign.com/signup?planId=1018&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Sign up for BoldSign today</a> and select the <strong>AU Region</strong> as your preferred data center location.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 6, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6c74632787c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/boldsign-data-center-australia-overview-d6c74632787c">BoldSign’s Dedicated Australian Data Center is Now Live!</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrate eSignatures into your Java apps with the BoldSign Java SDK]]></title>
            <link>https://medium.com/boldsign/boldsign-java-sdk-integrate-esignatures-580bc5c96477?source=rss----2834968ad290---4</link>
            <guid isPermaLink="false">https://medium.com/p/580bc5c96477</guid>
            <category><![CDATA[javasdk]]></category>
            <category><![CDATA[javaintegration]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[esignatures]]></category>
            <category><![CDATA[esignature-integration]]></category>
            <dc:creator><![CDATA[Reethika Moovendhan]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 06:02:51 GMT</pubDate>
            <atom:updated>2026-03-30T06:02:49.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Integrate eSignatures into your Java apps with the BoldSign Java SDK" src="https://cdn-images-1.medium.com/max/768/1*Ifnm9xRkthl3-Bm16LgBWg.png" /></figure><p>The BoldSign API already powers eSignature workflows for thousands of businesses. Now, with the <strong>BoldSign Java SDK</strong>, Java developers can easily bring eSignature capabilities into their applications with clean methods, strong typing, and minimal setup.</p><h3>Why a Java SDK?</h3><p>Java remains the backbone of mission-critical systems, enterprise applications, and SaaS platforms across the globe. Many developers asked for a library that feels native to Java, and we delivered. The BoldSign Java SDK is designed to reduce complexity and accelerate development.</p><p>Instead of writing request code manually, the SDK offers:</p><ul><li><strong>Simple method calls</strong> that map directly to BoldSign features.</li><li><strong>Strongly typed models</strong> and classes to catch errors early.</li><li><strong>Minimal boilerplate</strong> so you can focus on your core logic.</li></ul><h3>Key capabilities of the BoldSign Java SDK</h3><p>The SDK brings the full power of BoldSign within your Java projects and allows you to:</p><ul><li><strong>Send documents for signature</strong>: Upload contracts, agreements, or NDAs, define recipients, and request signatures — all in just a few lines of code.</li><li><strong>Manage templates</strong>: Reuse document templates for recurring workflows or combine multiple templates when needed.</li><li><strong>Track document status</strong>: Know instantly whether a signer has opened, signed, or declined a request.</li><li><strong>Set recipients and signing order</strong>: Add one or multiple signers, assign roles, and define signing order programmatically.</li><li><strong>Access audit trails and completed files</strong>: Download signed PDFs and retrieve detailed audit logs for compliance and recordkeeping.</li></ul><h3>Quick start example</h3><p>Here’s a simple example showing how to send a document for signature using the SDK:</p><pre>import com.boldsign.Configuration;<br>import com.boldsign.api.DocumentApi;<br>import com.boldsign.model.*;<br>import com.boldsign.model.FormField.FieldTypeEnum;<br><br>public class Example <br>{<br>    public static void main(String[] args) throws ApiException <br>    {<br>        ApiClient apiClient = Configuration.getDefaultApiClient();<br>        apiClient.setApiKey(&quot;YOUR_API_KEY&quot;);<br>        DocumentApi documentApi = new DocumentApi(apiClient);<br><br>        List&lt;File&gt; files = new ArrayList&lt;File&gt;();<br>        File file = new File(&quot;examples/documents/agreement.pdf&quot;);<br>        files.add(file);<br><br>        List&lt;FormField&gt; formFields = new ArrayList&lt;FormField&gt;();<br><br>        FormField signatureField = new FormField();<br>        signatureField.setFieldType(FieldTypeEnum.SIGNATURE);<br>        signatureField.setPageNumber(1);<br>        Rectangle rectangle = new Rectangle().x(100f).y(100f).width(100f).height(50f);<br>        signatureField.setBounds(rectangle);<br>        formFields.add(signatureField);<br><br>        List&lt;DocumentSigner&gt; signers = new ArrayList&lt;DocumentSigner&gt;();<br><br>        DocumentSigner signer = new DocumentSigner();<br>        signer.setName(&quot;Signer&quot;);<br>        signer.setEmailAddress(&quot;hankwhite@cubeflakes.com&quot;);<br>        signer.setFormFields(formFields);<br>        signers.add(signer);<br><br>        SendForSign sendForSign = new SendForSign();<br>        sendForSign.setTitle(&quot;Agreement&quot;);<br>        sendForSign.setFiles(files);<br>        sendForSign.setSigners(signers);<br><br>        DocumentCreated document = documentApi.sendDocument(sendForSign);<br>        System.out.println(document.getDocumentId());<br>    }<br>}</pre><p>With just a few lines of code, you’re sending documents for signature — fully integrated with BoldSign.</p><h3>Benefits for your development team</h3><p>Integrating BoldSign with your Java application isn’t just fast — it’s smart. Here’s how your team benefits:</p><ul><li><strong>Faster development</strong>: Add eSignature functionality in minutes with minimal setup.</li><li><strong>Reduced errors</strong>: Strong typing and clear models help ensure you’re using methods correctly.</li><li><strong>Flexible use</strong>: Whether you’re building enterprise apps, microservices, or lightweight utilities, the SDK fits right in.</li><li><strong>Safe testing environment</strong>: Use our free sandbox before pushing live.</li></ul><h3>Getting started with the BoldSign Java SDK</h3><p>Follow these simple steps to integrate <strong>BoldSign</strong> into your Java application.</p><h4>Step 1: Install the SDK</h4><p><strong>Maven setup</strong></p><p>Add this dependency to your project’s pom.xml:</p><p><strong>Pom.xml</strong></p><pre>&lt;dependency&gt;<br>  &lt;groupId&gt;com.boldsign&lt;/groupId&gt;<br>  &lt;artifactId&gt;boldsign-java&lt;/artifactId&gt;<br>  &lt;version&gt;1.0.3&lt;/version&gt;<br>  &lt;scope&gt;compile&lt;/scope&gt;<br>&lt;/dependency&gt;</pre><p>Find the latest version on <a href="https://central.sonatype.com/artifact/com.boldsign/boldsign-java?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Maven Central</a>. To install locally, execute:</p><p><strong>Install</strong></p><pre>mvn clean install</pre><p>To deploy to a remote Maven repository, execute:</p><p><strong>Deploy</strong></p><pre>mvn clean deploy</pre><p>(Make sure your pom.xml or settings.xml is configured — see the <a href="https://central.sonatype.org/publish/publish-guide?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">OSSRH guide</a>.)</p><p><strong>Gradle setup</strong></p><p>Add this to your build.gradle:</p><pre>repositories {<br>    mavenCentral()     // Needed if the &#39;boldsign-java&#39; jar has been published to maven central.<br>    mavenLocal()       // Needed if the &#39;boldsign-java&#39; jar has been published to the local maven repo.<br>  }<br><br>  dependencies {<br>     implementation &quot;com.boldsign:boldsign-java:1.0.3&quot;<br>  }</pre><p>Build and run on Windows:</p><pre>.\gradlew.bat clean build<br>.\gradlew.bat run</pre><h4>Step 2: Generate your API key</h4><p>To authenticate API requests:</p><ol><li>Sign up for a <a href="https://account.boldsign.com/signup?planId=1076&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">free BoldSign sandbox account</a>.</li><li>Generate your API key from the BoldSign dashboard. Refer to the <a href="https://developers.boldsign.com/authentication/api-key/?region=us&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">API key generation guide</a> for assistance.</li></ol><h4>Step 3: Start building</h4><p>Explore the <a href="https://developers.boldsign.com/documents/send-document/?region=us&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Java SDK documentation</a> for more examples and setup guides.</p><h3>Conclusion</h3><p>The BoldSign Java SDK makes it straightforward to bring secure, legally binding eSignatures into your Java applications. Whether you’re building enterprise systems, SaaS platforms, or custom tools, the SDK helps you deliver a smooth signing experience quickly.</p><p>Sign up for a <a href="https://account.boldsign.com/signup?planId=1076&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">free sandbox account</a> to explore these features. For support, contact our team via the <a href="https://support.boldsign.com/support/tickets/create?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">support portal</a> or schedule a personalized <a href="https://boldsign.com/request-demo?utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">demo</a>. You can also visit the <a href="https://developers.boldsign.com/sdks/java-sdk/?region=us&amp;utm_source=medium&amp;utm_medium=referral&amp;utm_campaign=repurposed_blogs">Java SDK documentation</a> for detailed setup instructions, code examples, and API references.</p><p>Originally published at <a href="https://boldsign.com/">https://boldsign.com/</a> on October 1, 2025</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=580bc5c96477" width="1" height="1" alt=""><hr><p><a href="https://medium.com/boldsign/boldsign-java-sdk-integrate-esignatures-580bc5c96477">Integrate eSignatures into your Java apps with the BoldSign Java SDK</a> was originally published in <a href="https://medium.com/boldsign">BoldSign</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>